Skip to content

README: the outside implementation, Tenuo v0.3.2 receipt chains, 25 scenarios - #32

Merged
pete-builds merged 1 commit into
mainfrom
docs/readme-accuracy
Oct 4, 2026
Merged

pete-builds merged 1 commit into
mainfrom
docs/readme-accuracy

Conversation

@pete-builds

Copy link
Copy Markdown
Owner

Three README claims were out of date. This PR changes seven lines and nothing else.

1. "Anyone outside the project": there is one, with caveats

Line 124 said the project has no one outside it, and the "Two implementations, one author" limit implied the same. Griffin Long's writ-ts is an outside implementation (#22). Both places now say so, with the caveats it states itself, each checked against #22:

  • An AI coding agent wrote it, "a Claude model", so "possibly not a different model family from your tooling".
  • Its verifier is not a blind result. It passed all 213 vectors at 6552968, but it saw them while it was being built.
  • Its executor's first run was blind: 19 of 22 scenarios, 136 of 140 steps. The three misses had one cause, in writ-ts.
  • It no longer conforms. It predates the ack a revoke's answer now carries (spec 9.4) and the total bound.

2. Tenuo: v0.2 is now v0.3.2, and its receipts can be chained

The row and the bullet said v0.2. Checked against Tenuo's own source and changelog:

  • v0.3.2 is the current release (GitHub release 2026-10-03; changelog dated 2026-10-02). It is the first release that contains Publish holder signing, approval hashes, and receipt chains; stop logging denials by default tenuo-ai/tenuo#758, merged 2026-09-30. v0.3.1 (2026-09-24) does not contain it.
  • What #758 added is receipt::verify_chain. It checks that a run of receipts has one signer and that each one's prev_receipt_hash is the digest of the one before it (tenuo-core/src/receipt.rs:693 at v0.3.2).
  • The field itself is older. prev_receipt_hash was already in the receipt format at v0.2.5. Its doc comment says "Chaining makes deletion detectable", so an enforcement point cannot quietly drop a decision (receipt.rs, payload key 14).
  • A receipt is still evidence of allow or deny: outcome is Allow or Deny, about "one authorization decision". Receipts are still opt-in (Tenuo README line 275; the receipts feature is off by default).

Why this is not a receipt tree across agents. A Tenuo chain is one enforcement point's decisions in time order. A Writ tree holds the receipts of every agent a delegation reached, each signed by the agent that did the work and embedded in its delegator's receipt. The "Combined differently" bullet and the table's "Sub-tree of receipts" cell now say that.

3. 24 scenarios is now 25

The cross-run table said 24; conformance/scenarios/ has 25.

Left out on purpose

The README says "28" Python-generated vectors on lines 303 and 314; there are 32. Line 314 sits between this PR's line 315 and #31's line 313, and a trial merge showed that editing it makes the two PRs conflict. It is a one-line follow-up after both merge.

Rebase

The edits are on lines 124, 161, 168, 193, 201, 240, and 315. Trial merges came out clean with #31, #28, #29, and #30, each paired with this branch.

🤖 Generated with Claude Code

…cenarios

- Line 124 and the "Two implementations, one author" limit said nobody
  outside the project had implemented Writ. Griffin Long's writ-ts has
  (issue #22), with the caveats it states itself: an AI agent wrote it,
  possibly from the same model family; its verifier saw the 213 vectors
  it passes; its executor's blind first run passed 19 of 22 scenarios
  (136 of 140 steps); and it no longer conforms since the ack and total.
- Tenuo row and bullet said v0.2. v0.3.2 (released 2026-10-03) adds
  receipt::verify_chain (tenuo-ai/tenuo#758): one signer's receipts
  linked by prev_receipt_hash, still evidence of allow or deny. Says why
  that is not a receipt tree across agents.
- The cross-run table said 24 scenarios; the corpus has 25.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@pete-builds
pete-builds merged commit 9a9b885 into main Oct 4, 2026
11 checks passed
@pete-builds
pete-builds deleted the docs/readme-accuracy branch October 4, 2026 21:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant