Repository navigation
Amend ADR 0005 D4/D5: core Lean and Rocq are §2 recheck legs - #124
Conversation
The owner chose, 2026-11-17, from the selector after #122: "Count it + amend ADR 0005 D4". This records the ruling in the ADR, so the ADR and PROOF-POLICY §2 stop disagreeing on paper. ADR 0005 gains an amendment section recording two rulings: - 2026-11-09: Lean + Mathlib is a generator, never a leg, and its rows stay BRIDGE-PENDING. - 2026-11-17: theory is rechecked in Rocq and Lean with no Mathlib, and the 2026-11-09 ruling does not cover a Lean leg that imports nothing. D4 as amended separates the two Lean roles (core = recheck leg, Mathlib = generator) and adds Rocq as a recheck leg. D5 as amended: the template removal stands, but the repository now has four proof developments. The Rocq leg is instantiated and gated, not a template. PROOF-STATUS, README and CHANGELOG drop the "put to the owner" wording from #122 and point to the amendment. No grade moves: the ledger already followed this ruling. pwg-check PASS; asciidoctor 2.0.20 renders all four files with no warning. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01J4QvDf73vaDJwGZ3qMSeH3
|
Fork governance
Scope: the three lanes below are static checks at the named commit. A K9-DEED conformance🟡 advisory · commit
K9 live corpus (L0–L2): 8 finding(s) / scope notes
Scope: K9 components L0–L2 against contract v1.0.0 at the named standards commit. L3 signature verification and routed coordination-dialect files are not certified. Green is limited to this scope. Orange is missing evidence; yellow is grandfathered debt or warnings; grey is an explicit scope exclusion. report.json, badge.json and the validator logs are in the k9-grid artifact on the linked run. Hypatia verdict grid🟢 clean · commit Advisory: 11 row(s), worst 🔴 high (0 critical, 9 high in grid scope) — reported, never grading the change. Unique graded findings across gating and advisory rows: 25 (25 reporter observations; 21 without sufficient identity to corroborate). Row counts remain per reporter; unique totals do not change gating.
Hypatia scan: 13 finding(s)
panic-attack assail: 3 finding(s)
echidnabot: not_applicable — proofs here are gated by their own toolchains (proofs.yml: Idris2, Lean, Agda); no ECHIDNA engine is configured, so this adapter could only ever report not_run
rhodibot (RSR compliance): 11 finding(s)
panicbot: not_applicable — panic-attack already reports directly as its own row in the Hypatia verdict grid; enrolling panicbot would count the same findings twice
sustainabot: not_applicable — reserved fleet slot; no adapter exists (gitbot-fleet README)
glambot (presentation quality): 82 finding(s)
seambot: not_applicable — no seam register is declared (spec/seams/seam-register.json)
finishingbot (release readiness): 127 finding(s)
cipherbot: not_applicable — no cryptography is implemented in this repository; the hashes present are checksum/integrity pins, which cipherbot would report as cryptographic findings
accessibilitybot: not_applicable — no served HTML surface; this is a checker library/CLI with AsciiDoc documentation
Scope: static findings reported by each row's tool at the named commit. The table grades only findings in files this change touches, so the colour answers "does this change introduce anything?", not "what does the whole repository still carry?". Standing findings are counted in each accordion and in report.json; the baseline filter remains the place where acknowledged debt is recorded. The lane state is the worst GATING row; advisory rows are listed and counted but never set it. Purple, red, yellow and blue grade the worst GRADED finding present; orange is evidence missing, malformed or a scanner that did not run; grey is an explicit scope exclusion with its reason. No row is a security certification. report.json, badge.json and the raw findings are in the verdict-grid artifact on the linked run. |



Summary
This is a follow-up to #122, which merged into this base. Before #122 merged, the owner chose "Count it + amend ADR 0005 D4" in the selector. That decision settles whether a Lean recheck leg with no Mathlib may count, given the 2026-11-09 ruling "Lean is a generator, not a leg". This PR writes the decision into ADR 0005, so the ADR and PROOF-POLICY §2 stop disagreeing on paper.
No grade moves. The ledger already followed this ruling. The census is unchanged: of 28,
PWG-315,PWG-2ii7,ungraded6.Changes
+foundation-diversetag.just proof-statusand the other D5 recipes still say "three provers" (doctrine 16).RSR Quality Checklist
Required
pwg-check.shPASS, with table and census unchanged--failure-level=WARNon all four filesunsafeblocks without// SAFETY:comments.envfiles includedAs Applicable
docs/decisions/updatedCHANGELOGupdatedTesting
No proof file changed, so no kernel run is needed or claimed.
Generated by Claude Code