Repository navigation
docs: accurate Interlock tagline; re-date evidence (27 tests, 2026-10-15) - #10
Conversation
…-15) Tagline 'Interlock proves what it did' -> 'Interlock says for how long': Interlock's own README says its ledger is not hash-chained or signed and is an audit log, not tamper evidence. Re-ran unittest on main at 5c941da (27 OK) and examples/subpoena_week.py (chain intact: True). Docs only.
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5dcc136150
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| [](https://github.com/FetchDoge/governor/actions/workflows/ci.yml) [](LICENSE) [](pyproject.toml) | ||
|
|
||
| > *Permit says what an agent may spend. Governor says what it may do. Interlock proves what it did.* | ||
| > *Permit says what an agent may spend. Governor says what it may do. Interlock says for how long.* |
There was a problem hiding this comment.
This now describes Interlock as controlling duration, but the repository consistently defines it as the external receipt ledger: ROADMAP.md says sending receipts there makes “Interlock proves” literally true, THREAT_MODEL.md identifies it as the intended append-only sink, and docs/BRAINSTORM.md still calls it the evidence/provenance layer. Publishing the new wording therefore misstates the component's role and leaves the stack story internally contradictory; keep the evidence-oriented wording unless the associated architecture documentation is also being changed.
Useful? React with 👍 / 👎.
1 participant
Tagline 'Interlock proves what it did' -> 'Interlock says for how long': Interlock's own README says its ledger is not hash-chained or signed and is an audit log, not tamper evidence. Re-ran unittest on main at 5c941da (27 OK) and examples/subpoena_week.py (chain intact: True). Docs only.