v0.11 item 4: G31, the catalogue at v7, and three transcripts re-run - #32
Merged
Merged
Conversation
… entry it pays The generators pick up `StateStore.receipts()` returning `Receipt | UnreadableReceipt` and the line numbers item 1 moved. ROADMAP's known-limitation entry for the malformed value is closed, with the two corrections implementing it earned: it listed G11 among the blinded readers, and `ctrlrun verify` grades G11 against a scratch store no UPDATE reaches; and it omitted the operator MCP server, which is a network surface. Signed-off-by: arpan <contact@arpanghoshal.com>
The page this milestone most changes, in the operator's own terms. Signed-off-by: arpan <contact@arpanghoshal.com>
CI installs the kernel as [dev,gateway,otel,identity] and no postgres extra, so it collects 6,096 where a local checkout with psycopg installed collects 6,172. The committed block is the one CI checks, so it is generated where CI generates it. Signed-off-by: arpan <contact@arpanghoshal.com>
CTRLRun/ctrlrun#200 merged with no paired docs branch, so main's docs job has been red since: the api reference and CLAIMS.md both cite line numbers that moved when _read_receipt grew, and the readiness block counts the eight tests it added. Branched from v0.11/1-unreadable-receipt rather than main, so merging this lands item 1's pages and these together and main goes green in one step. Signed-off-by: arpan <contact@arpanghoshal.com>
The three quoted `ctrlrun verify` transcripts are refreshed from real runs against their own policies, not edited: docs/verify.md against examples/authority/payments.yaml, and the CI guide and cookbook page against the policy each of them quotes. ROADMAP's 'nothing yet proves' sentence is closed, with the methodology error the proof made first: PYTHONPATH is inherited by every child, so all five released wheels imported the build under test and the run reported one schema version while looking exactly like a pass. Signed-off-by: arpan <contact@arpanghoshal.com>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
|
Warning Review limit reachedNext included review available in 50 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: ⛔ Files ignored due to path filters (4)
📒 Files selected for processing (25)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pairs with CTRLRun/ctrlrun#201, on a branch of the same name. v0.11 item 4: one chain, five receipt schema versions.
Stacks on #31. That PR is what makes docs
maingreen again after kernel #199 and #200; this contains its commits, so merging #31 first and then this, or just this, both work.The three quoted verify transcripts are re-run, not edited
This is the change most worth checking, because
test_every_quoted_verify_transcript_is_one_verify_actually_printsexists precisely because both of these pages were once written rather than captured.docs/verify.mdexamples/authority/payments.yaml, now25/25, cataloguev7docs/cookbook/verify-in-github-actions.mdx16/16docs/guides/verify-in-ci.mdx<Steps>blockEach was produced by running
ctrlrun verifyagainst that page's own policy with item 4's kernel branch installed, and pasting what it printed.docs/verify.md's abridged N/A illustration moves from8/8 … never 16/16to9/9 … never 17/17:G31needs only an action to build a chain from, so it is applicable wherever any guarantee is, andtests/test_verify_page.pyis updated to pin the new number.Written by hand
docs/OWASP-AGENTIC-TOP10.mdgainsG31's row underASI09:2026(partly), alongsideG11. What it says it does not close is the part worth reading: this is about whether the record can still be read and recomputed years later, not about who wrote it, and an unknown schema label is named so an operator knows which row this binary could not fully interpret, which is a different sentence from this row was tampered with.docs/ROADMAP.md's v0.11 bullet said "nothing yet proves that verify walks it end to end". It is closed and dated, and it carries the methodology error the proof made first, so the next person building a multi-version proof does not rediscover it:ROADMAP.mdalready said five receipt schema versions in both the prose and the Exit line, soSPEC-v0.11.md§6's instruction to correct "four" had already been carried out by an earlier session and nothing needed changing.Generated
Every generator re-run against the item 4 kernel branch, then
repoint-claims.py, then both readiness blocks pasted fresh. The readiness block now reads 28 guarantees and 6,122 tests.One thing worth recording about how that was produced. The generators were first run in a virtual environment holding kernel
main, which has 27 guarantees, so the readiness block came out saying 27 while the catalogue under test had 28 — andtest_no_page_states_a_guarantee_count_the_catalogue_does_not_havecaught it. The environment must hold the branch being documented, built the way docs CI builds one:[dev,gateway,otel,identity]and nopostgresextra.git statusin the kernel worktree after running every generator: clean.Checks
./scripts/check.sh: 1701 passed.🤖 Generated with Claude Code