Skip to content

Amend ADR 0005 D4/D5: core Lean and Rocq are §2 recheck legs - #124

Merged
hyperpolymath merged 1 commit into
claude/pwg-names-ladderfrom
claude/adr-0005-d4-lean-recheck
Nov 17, 2026
Merged

hyperpolymath merged 1 commit into
claude/pwg-names-ladderfrom
claude/adr-0005-d4-lean-recheck

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

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-3 15, PWG-2ii 7, ungraded 6.

Changes

  • ADR 0005: an amendment section dated 2026-11-17.
    • It records both rulings. On 2026-11-09: Lean with Mathlib is a generator, never a leg. On 2026-11-17: theory is rechecked in Rocq and Lean with no Mathlib, and a Lean leg that imports nothing is a §2 recheck leg.
    • D4 as amended gives a role table: Agda is the normative kernel; Rocq is a recheck leg; core Lean is a recheck leg; Lean with Mathlib is a generator; Idris2 is the reference; Rust is the fast core. The table notes that core Lean does not earn §8.3's +foundation-diverse tag.
    • D5 as amended: the template removal stands. The 2026-11-17 Rocq file is an instantiated, gated recheck leg, so the repository has four proof developments, not three.
    • It names the out-of-scope upkeep: just proof-status and the other D5 recipes still say "three provers" (doctrine 16).
  • PROOF-STATUS, README, CHANGELOG: the "put to the owner" wording from Prove L4 in full and A2 (Fate is a chain); recheck both in Rocq and core Lean #122 is replaced with the ruling and a pointer to the amendment.

RSR Quality Checklist

Required

  • Tests pass: pwg-check.sh PASS, with table and census unchanged
  • Code is formatted (docs only)
  • Linter is clean: asciidoctor 2.0.20 with --failure-level=WARN on all four files
  • No banned language patterns
  • No unsafe blocks without // SAFETY: comments
  • No banned functions
  • SPDX license headers present (unchanged)
  • No secrets, credentials, or .env files included

As Applicable

  • docs/decisions/ updated
  • Documentation updated
  • CHANGELOG updated

Testing

bash scripts/pwg-check.sh   -> PASS ... 29 obligation(s) derived, published table and census match
asciidoctor -o /dev/null --failure-level=WARN <each of the 4 files>   -> exit 0

No proof file changed, so no kernel run is needed or claimed.


Generated by Claude Code

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
@sonarqubecloud

Copy link
Copy Markdown

@github-actions

Copy link
Copy Markdown

Fork governance

Lane Status Run
DEED syntax (repo deed) 🟢 conformant run 44021827312
K9-DEED conformance (L0–L2; L3 not verified) 🟡 conformant (advisory debt) (job: success) same run
Hypatia verdict grid 🟢 no graded findings (job: success) · advisory in grid scope: 🔴 red (0 critical, 9 high, not grading) same run

Scope: the three lanes below are static checks at the named commit. A
green row means every applicable check in its declared scope passed;
orange means evidence is missing, not that nothing was found. The
Hypatia verdict covers GATING rows only; advisory reporters are listed
in its grid and their severity counts are limited to the grid scope.
A blocking gate may inspect findings outside the delta grid’s grade; open
the linked run and check annotations for the failing step and, where
applicable, the finding. No row is a security certification.

K9-DEED conformance

k9-deed L0–L2 yellow

🟡 advisory · commit 51adf7f95c40 · run 44021827312 · validator hyperpolymath/standards@857ff096af11

Category Status Pass Fail Indeterminate N/A Since previous revision
K9 contract typecheck 🟢 conformant 1 0 0 0 — no comparable baseline
K9 validator self-test 🟢 conformant 49 0 0 0 — no comparable baseline
K9 live corpus (L0–L2) 🟡 advisory 2 8 (8 advisory) 0 0 — no comparable baseline
K9 live corpus (L0–L2): 8 finding(s) / scope notes
  • .machine_readable/self-validating/examples/setup-repo.k9.ncl — fail (advisory): K9-S007: security flags request capabilities the grant does not cover: net.fetch fs.write process.spawn (default-deny: list them in pedigree.security.capabilities); K9-S009: leash is 'Hunt but no pedigree.signature block is present (presence required here; verificatio
  • .machine_readable/self-validating/methodology-guard.k9.ncl — fail (advisory): K9-S002: pedigree.schema_version is missing; K9-S003: pedigree.component_type is missing (required by contract v1.0.0 §6.2); K9-N001: component violates the K9.Component contract: error: missing definition for `schema_version` ┌─ /home/runner/work/
  • .machine_readable/self-validating/template-hunt.k9.ncl — fail (advisory): K9-S003: pedigree.component_type is an unfilled placeholder: 'TODO: describe component type (e.g., 'deployment', 'setup-script')'; K9-S005: pedigree.metadata.name is an unfilled placeholder: 'TODO: component-name'; K9-S007: security flags request capabilities the gran
  • .machine_readable/self-validating/template-kennel.k9.ncl — fail (advisory): K9-S003: pedigree.component_type is an unfilled placeholder: 'TODO: describe component type (e.g., 'build-config', 'metadata')'; K9-S005: pedigree.metadata.name is an unfilled placeholder: 'TODO: component-name'
  • .machine_readable/self-validating/template-yard.k9.ncl — fail (advisory): K9-S003: pedigree.component_type is an unfilled placeholder: 'TODO: describe component type (e.g., 'validated-config', 'schema')'; K9-S005: pedigree.metadata.name is an unfilled placeholder: 'TODO: component-name'
  • container/deploy.k9.ncl — fail (advisory): K9-S002: pedigree.schema_version is missing; K9-S003: pedigree.component_type is missing (required by contract v1.0.0 §6.2); K9-S004: pedigree.security.leash is missing; K9-S005: pedigree.metadata.name is missing; K9-S011: component declares a 'recipes' block at l
  • coordination.k9 — fail (advisory): K9-S002: pedigree.schema_version is missing; K9-S003: pedigree.component_type is missing (required by contract v1.0.0 §6.2); K9-N001: component does not typecheck against K9.Component: error: unexpected token ┌─ /home/runner/work/trope-checker/trope-checker/.k9-
  • session/custom-checks.k9 — fail (advisory): K9-S002: pedigree.schema_version is missing; K9-S003: pedigree.component_type is missing (required by contract v1.0.0 §6.2); K9-N001: component does not typecheck against K9.Component: error: unexpected token ┌─ /home/runner/work/trope-checker/trope-checker/sess

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

Hypatia grid green

🟢 clean · commit 51adf7f95c40 · run 44021827312 · scope: this change (4 file(s))

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.
Raw Hypatia alert-derived observations: 43 (code-scanning, Dependabot and secret-scanning; some may also be in SARIF; not an extra total).

Reporter Gate Status Critical High Medium Minor Since previous revision
Hypatia scan gating 🟢 clean 0 0 0 0 — no comparable baseline (no prior PR grid or unreadable snapshot)
panic-attack assail advisory 🟢 clean 0 0 0 0 — no comparable baseline (no prior PR grid or unreadable snapshot)
pons asinorum advisory 🟢 clean 0 0 0 0 — no comparable baseline (no prior PR grid or unreadable snapshot)
echidnabot advisory ⚪ not applicable 0 0 0 0 — no comparable baseline (no prior PR grid or unreadable snapshot)
rhodibot (RSR compliance) advisory 🟢 clean 0 0 0 0 — no comparable baseline (no prior PR grid or unreadable snapshot)
panicbot advisory ⚪ not applicable 0 0 0 0 — no comparable baseline (no prior PR grid or unreadable snapshot)
sustainabot advisory ⚪ not applicable 0 0 0 0 — no comparable baseline (no prior PR grid or unreadable snapshot)
glambot (presentation quality) advisory 🔵 minor 0 0 0 9 — no comparable baseline (no prior PR grid or unreadable snapshot)
seambot advisory ⚪ not applicable 0 0 0 0 — no comparable baseline (no prior PR grid or unreadable snapshot)
finishingbot (release readiness) advisory 🔴 high 0 9 5 2 — no comparable baseline (no prior PR grid or unreadable snapshot)
cipherbot advisory ⚪ not applicable 0 0 0 0 — no comparable baseline (no prior PR grid or unreadable snapshot)
accessibilitybot advisory ⚪ not applicable 0 0 0 0 — no comparable baseline (no prior PR grid or unreadable snapshot)
Hypatia scan: 13 finding(s)
  • 13 further finding(s) in files this change does not touch: reported, not graded (0 critical, 0 high).
panic-attack assail: 3 finding(s)
  • 3 further finding(s) in files this change does not touch: reported, not graded (0 critical, 0 high).
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
  • ⚪ 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)
  • 11 further finding(s) in files this change does not touch: reported, not graded (0 critical, 11 high).
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
  • ⚪ 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)
  • ⚪ not applicable: reserved fleet slot; no adapter exists (gitbot-fleet README)
glambot (presentation quality): 82 finding(s)
  • info GS-001 — Install git-seo for comprehensive SEO analysis: https://github.com/hyperpolymath/git-seo
  • info MACH-007 — ECOSYSTEM.scm not found in .machine_readable/ directory.
  • info MACH-007 — META.scm not found in .machine_readable/ directory.
  • info MACH-007 — STATE.scm not found in .machine_readable/ directory.
  • info MACH-005 — No robots.txt found. Consider adding one for crawler control.
  • info VIS-005 — docs/decisions/0005-v0.2-consolidation-o5-and-prover-roles.adoc:1 — Line 97 characters exceeds max length of 80.
  • info VIS-005 — docs/status/PROOF-STATUS.adoc:1 — Line 97 characters exceeds max length of 80.
  • info VIS-005 — CHANGELOG.adoc:17 — Line 82 characters exceeds max length of 80.
  • info VIS-005 — README.adoc:1 — Line 97 characters exceeds max length of 80.
  • 73 further finding(s) in files this change does not touch: reported, not graded (0 critical, 2 high).
seambot: not_applicable — no seam register is declared (spec/seams/seam-register.json)
  • ⚪ not applicable: no seam register is declared (spec/seams/seam-register.json)
finishingbot (release readiness): 127 finding(s)
  • high V1-DOC-ROADMAP.adoc — Required file ROADMAP.adoc not found (Project roadmap).
  • high TOOL-001 — .tool-versions file not found for asdf/mise version management.
  • high SCM-001-NEUROSYM.scm — Required SCM file NEUROSYM.scm not found (Neurosymbolic AI documentation).
  • high SCM-001-AGENTIC.scm — Required SCM file AGENTIC.scm not found (Agentic AI integration documentation).
  • high SCM-001-PLAYBOOK.scm — Required SCM file PLAYBOOK.scm not found (Operational playbooks and procedures).
  • high SCM-001-ECOSYSTEM.scm — Required SCM file ECOSYSTEM.scm not found (Project's place in the ecosystem).
  • high SCM-001-META.scm — Required SCM file META.scm not found (Meta-level information and architectural decisions).
  • high SCM-001-STATE.scm — Required SCM file STATE.scm not found (Project state and progress tracking).
  • high PH-100 — Found 102 placeholders, exceeds maximum allowed (0)
  • medium V1-COM-CONTRIBUTING.md — CONTRIBUTING.md file not found (Contribution guidelines).
  • medium V1-COM-CODE_OF_CONDUCT.md — CODE_OF_CONDUCT.md file not found (Code of conduct).
  • medium V1-SEC-001 — SECURITY.md not found for responsible disclosure.
  • medium TEST-AG-002 — No direct single-line Agda source check was identified in the known workflow or recipe locations. Dynamic runners need separate review; no proof was executed.
  • medium CLM-006 — docs/status/PROOF-STATUS.adoc — Documentation references non-existent file: lakefile.toml
  • info CLM-003 — README.adoc — README missing 'Usage examples' section
  • info CLM-003 — README.adoc — README missing 'Installation instructions' section
  • 111 further finding(s) in files this change does not touch: reported, not graded (0 critical, 1 high).
cipherbot: not_applicable — no cryptography is implemented in this repository; the hashes present are checksum/integrity pins, which cipherbot would report as cryptographic findings
  • ⚪ 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
  • ⚪ 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.

@hyperpolymath
hyperpolymath marked this pull request as ready for review November 17, 2026 13:53
Repository owner deleted a comment from coderabbitai Bot Nov 17, 2026
Repository owner deleted a comment from chatgpt-codex-connector Bot Nov 17, 2026
Repository owner deleted a comment from chatgpt-codex-connector Bot Nov 17, 2026
@hyperpolymath
hyperpolymath merged commit 6106878 into claude/pwg-names-ladder Nov 17, 2026
41 checks passed
@hyperpolymath
hyperpolymath deleted the claude/adr-0005-d4-lean-recheck branch November 17, 2026 13:59
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.

3 participants