Repository navigation
Show Comparator's evidence under each declaration it checked - #21
Merged
Merged
Conversation
The build reads a Comparator run's files from the folder `[comparator] evidence` names in paper.toml, so the four PCP pages share papers/pcp-full-argument/comparator. It stops if a file differs from receipt.json's SHA-256, if the challenge states no theorem of a configured name, or if the receipt records no accepted run and rejected control. For each theorem name it emits the challenge statement, its lines and links fixed at the built commit. Each checked declaration gets a closed "Comparator evidence" fold under its axiom report: the result and run facts, the challenge statement, links to the solution, receipt, configuration and Actions run, the rejected control and the scope. The index at the back counts and links the checked statements. Line lookups for the reading thread skip the challenge's own line numbers. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Wherever the reader shows one of the three theorems Comparator checked (
PCP.np_subset_pcp,PCP.pcp_subset_np_concrete,PCP.ReferenceNP.inNP_iff_mem), the declaration now has a closed Comparator evidence fold under its axiom report.Build (
tools/paper.py):[comparator] evidence = "<folder>"in paper.toml names the run's files; the four PCP pages sharepapers/pcp-full-argument/comparator. The build checks each file againstreceipt.json's SHA-256, that the configuration and receipt name the same theorems and permitted axioms, that the run was accepted and the control rejected, and thatChallenge.leanstates every configured theorem. It emits each statement with its lines and links fixed at the built commit (GITHUB_SHAin Actions). Unit tests cover the failure cases.Page: result and run facts once, what Comparator tested, the challenge statement as a Lean listing with a link to its lines, links to the solution, receipt, configuration and Actions run, the rejected control, and a scope line. The index at the back counts and links the checked statements. The reading thread and the step scroll now skip the challenge's own line numbers.
No other paper has Comparator files;
contextual-embeddingsis unchanged.Checks: unit tests (130),
paper.py checkon all five papers,paper.py build,npm run test:source, site build,tests/journey.py(445 checks), and a Playwright check of every fold at 1440x860 and 390x844 (195 checks).🤖 Generated with Claude Code