Repository navigation
docs(proofs): per-statement placement of the engineering proofs (split by property) - #518
Conversation
…t by property) Owner ruling 2026-11-16: each existing engineering proof statement goes where its property lives. docs/PROOF-PLACEMENT.adoc records the home of all 247 top-level statements in R9, R10, R4's engineering modules, the R3 Lean corpus and the Idris 2 verification corpus: rust (Creusot/Pearlite and Verus) 96 idris2 (interface / wire) 4 agda-theory 31 retire (with successor named) 116 Each rust row names its target function and the contract to discharge. Per area it lists the places where a proof models behaviour the Rust lacks, and the questions only the owner can settle. Produced in three passes, all read-only: a classifier per area, an adversarial reviewer per area, and a judge that reconciled the two against the source. Nothing was built or run (no Agda, Lean, Idris 2, Creusot, Verus or cargo), so this is a placement, not a receipt; it changes no PROOF-STATUS token. The defects it names are source readings that still need a failing test or a repro. The ledger was rendered mechanically from the reconciled JSON (jq), not hand-transcribed. PROOF-STATUS links it from the 2026-11-16 ruling paragraph. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019a95kk88TZ1iegsBK3kox3
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the
|
…/new-session-th4e9w-placement-ledger
Codex Review Summary: ❌ FailedThis 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. |
|
This security review couldn’t start because the paying account has exhausted its Codex allowance and has insufficient available credits. The payer can check their balance and add credits in the Codex usage dashboard, then try again. If you do not manage the paying account, contact this repository's admins. |
…/new-session-th4e9w-placement-ledger
…/new-session-th4e9w-placement-ledger
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 99941b9162
ℹ️ 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".
Codex on #518, three findings, all confirmed: - The census double-counted statements and gave some two homes. Four files were covered by two or three areas (ClampTrustBounds.idr and NatLte.idr by R10 and the Idris corpus; DispatchOrdering.idr by R9 and the Idris corpus; the key-* aliases in MetaChecker.agda by R9, R10 and R4). The 15 order lemmas were retire in one area and rust in the other, with the same successor contract. Each file now sits in one area (the finer-grained rows kept; the 23 aliases stay one retire row, since an alias proves nothing beyond its target); the order lemmas are retire, as the corpus row's own reason ("closed facts about literals") says. Census: 233 rows (92 rust, 4 idris2, 31 agda-theory, 106 retire), defined as one statement or a named group. - The method note said nothing was run, but one judge rechecked Agda probes on a scratch Agda 2.6.3. It now says no canonical check ran, names that recheck, and says it is not a receipt. - Two model gaps counted a verify_all error as an integrity fail-open path; verify_all only returns Ok (solver_integrity.rs:164-209), as the R9 analysis says. Both now say the case is unreachable. The ledger is re-rendered from the corrected JSON by the same jq generator; PROOF-STATUS quotes the new counts. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019a95kk88TZ1iegsBK3kox3
|
This security review couldn’t start because the paying account has exhausted its Codex allowance and has insufficient available credits. The payer can check their balance and add credits in the Codex usage dashboard, then try again. If you do not manage the paying account, contact this repository's admins. |
…/new-session-th4e9w-placement-ledger
|
This security review couldn’t start because the paying account has exhausted its Codex allowance and has insufficient available credits. The payer can check their balance and add credits in the Codex usage dashboard, then try again. If you do not manage the paying account, contact this repository's admins. |
|



Stacked on #514, which records the ruling. This PR adds the per-statement ledger.
Summary
Owner ruling 2026-11-16: split by property.
docs/PROOF-PLACEMENT.adocgives every top-level statement in R9, R10, R4's engineering modules, the R3 Lean corpus and the Idris 2 verification corpus exactly one home. A row is one statement or a named group of closely related declarations. A file covered by two areas appears in only one, so no statement has two homes.rust(Creusot/Pearlite and Verus; target function and contract named)idris2(interface or wire fact)agda-theoryretire(successor named)Each area also lists model gaps (places where a proof models behaviour the Rust lacks) and open questions (points only the owner can settle).
How it was produced
Three passes per area, all reading the source:
No canonical check ran and no receipt was produced. One judge rechecked a few Agda probes on a scratch Agda 2.6.3. The document is rendered mechanically from the judges' JSON with
jq. It is a placement, not a receipt, and no PROOF-STATUS token changes.Source readings that look like live holes
These are not yet confirmed by a test or repro, and none is fixed here.
with_integrity_checker(src/rust/dispatch.rs:317) has no caller.config/solver-manifest.tomlholdPLACEHOLDER_COMPUTE_ON_FIRST_RUN.solver_integrity_okis always true.src/rust/integrity/mod.rs:5-8claims a mismatched solver "will not be used".verify_proofkeeps only the first axiom usage (dispatch.rs:643-645), and the cross-checked path recomputes the danger from it (:851-855,:890).BayesianandDempsterShaferpolicies, a conclusive disagreement can still yield a verdict (result_arbiter.rs:374-431). Dispatch then returnsverified = true(dispatch.rs:899-900).Tamperedand on placeholders (solver_integrity.rs:250-253,:272-275).ProverKind-to-manifest key mapping fails forlean4andhol_light, and collidesMizARwithMizar.clamp_trust,max_level,combine_trust,min_level,is_solver_safeandquick_reverifyhave no caller outside tests.🤖 Generated with Claude Code
https://claude.ai/code/session_019a95kk88TZ1iegsBK3kox3