Skip to content

Run the aspect lane, tighten what a grade may stand on, narrow four status claims - #123

Merged
hyperpolymath merged 4 commits into
claude/stripper-nesting-psibondfrom
claude/gate-gaps-and-status-rows
Nov 17, 2026
Merged

hyperpolymath merged 4 commits into
claude/stripper-nesting-psibondfrom
claude/gate-gaps-and-status-rows

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

Summary

Stacked on #120 (which contains #119 and #117). Three groups of fixes from the 2026-11-16 proof audit. No proof statement, token or published grade changes: the census stays PWG-3 18, ungraded 10 of 28.

Changes

1. The aspect lane ran nothing

  • just aspect was the mint template. It printed "Aspect tests passed!" having run nothing, and test-all depends on it.
  • tests/aspect_tests.sh was invoked by no recipe and no workflow.
  • Its Idris2 scan read src/interface/Abi/ only (3 of 16 files) and dropped every hit containing "test".

Now: the recipe and the quality workflow run the script. The scan reads every Idris2 source under src/ and verification/ through the comment stripper, adds assert_smaller, unsafePerformIO, idris_crash and postulate, and fails when it finds no Idris2 file.

2. Grade derivation (scripts/pwg-derive.sh)

Gap Before After Policy
Axiom dispositions A leg reporting any axiom counted Counts only when each reported axiom has disposition c, recorded on the receipt as axiom_dispositions; none recorded is inadmissible §8.4 rule 6, §8.5.1
Derived axioms The Agda receipt's list alone Union over every witness the grade stands on §8.4 rule 6
Canonical invocation Three flag substrings anywhere in the string Each agda command is exactly the three flags and one module §2.1
+foundation-diverse Any non-null value An accepted, RECONCILED, receipted witness §8.3

scripts/pwg-check.sh rejects a disposition outside c|b|debt, and one recorded for an axiom the receipt does not report.

axiom_dispositions is a new optional receipt field. No disposition is recorded on the live Lean receipts: assigning one is a trusted-base decision, deferred to the owner. Those legs are BRIDGE-PENDING and do not count either way.

3. Status claims narrowed to their theorems

  • Veridicality Derivation: deceptiveDuals is a tuple value in both provers and is no longer cited as evidence.
  • Verdict soundness: verdictSound is over a grade-shaped floor, as its source says, not the use-model floor.
  • Tier-2 membership: names the ratified iff, GradeR.gradeR_leftCancel_iff.
  • README: no longer says PROOF-STATUS and pwg.json "agree row for row".
  • grade-factorisation README: the verdict is marked as the pre-ratification result and GradeFactorisationR.lean is listed.
  • grade-factorisation REPORT: states the measured axiom bound. The CI axiom audit of both modules at 7b71c31 (run 43981767344, 184 declarations) reported propext and Quot.sound only. The paragraph had quoted the audit's allowlist, which also admits Classical.choice.

Left out on purpose

Merge-coordinate separability and the L4Monotonicity.lean docstring belong to the separate proof work on L4/A2 and are untouched.

Found, not fixed

The ledger receipt lean-factorisation-c0eb4f1 lists Classical.choice among its axioms. The audit at 7b71c31 reports none for that package. I have not read the log of the receipt's own run (42623339243), so the receipt is unchanged.

RSR Quality Checklist

Required

  • Tests pass — see Testing
  • Code is formatted
  • Linter is clean — ShellCheck could not be run in my container; CI's code-quality job is the check
  • No banned language patterns
  • No unsafe blocks without // SAFETY: — n/a
  • No banned functions
  • SPDX license headers present — existing headers untouched
  • No secrets, credentials, or .env files included

As Applicable

  • Documentation updated — CHANGELOG entry
  • Repo deed, docs/decisions/ — not touched

Testing

Run in my container against this branch:

scripts/test-gate-falsifiability.sh   -> 43/43
scripts/pwg-check.sh                  -> PASS, 29 obligations, table and census match
tests/aspect_tests.sh                 -> PASS=3 FAIL=0, 16 Idris2 files scanned
jq -cS . verification/pwg.json | cmp  -> identical
tests/workflows/*_test.sh             -> both exit 0

Each new canary was run against the code before its fix:

canaries 32-34 vs pre-fix Justfile and aspect script  -> 31/34, all three fail
canaries 35-41 vs pre-fix pwg-derive.sh               -> 35/41, six fail (the seventh is a control)
canaries 42-43 vs pre-fix pwg-check.sh                -> 41/43, both fail

Not run here: Agda, Lean, Rocq or Idris2. No kernel result is claimed. The axiom bound quoted for grade-factorisation is read from the CI log named above.


Generated by Claude Code

`just aspect` was the mint template: it ran nothing and printed "Aspect
tests passed!", and `test-all` depends on it. tests/aspect_tests.sh was
invoked by nothing. Its Idris2 scan read src/interface/Abi/ only (3 of
16 files) and dropped every hit containing "test".

The recipe now runs the script, and the quality workflow runs it too.
The Idris2 scan reads every .idr under src/ and verification/ through
the comment stripper, adds assert_smaller, unsafePerformIO, idris_crash
and postulate to the banned set, and fails when it finds no Idris2 file.

Canaries 32-34 plant a banned construct in a path containing "test",
an Idris2-free tree, and check the recipe body. All three fail against
the pre-fix tree (31/34); the suite is 34/34.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01J4QvDim4mMEfCer9SiAV4H
Four gaps in scripts/pwg-derive.sh. None moves a published grade: the
census is unchanged at PWG-3 18, ungraded 10 of 28.

- Axiom dispositions (8.4 rule 6, 8.5.1). A leg whose current receipt
  reports an axiom counted whatever the axiom was. A leg now counts only
  when every reported axiom has disposition c, recorded on the receipt
  as axiom_dispositions; an axiom with none recorded is inadmissible.
  No disposition is recorded on the live Lean receipts here: assigning
  one is a trusted-base decision for the owner, and those legs are
  BRIDGE-PENDING and do not count either way.
- Derived axioms (8.4 rule 6). The list was the Agda receipt's alone, so
  a counting Rocq or Lean leg added to the count and hid its axioms. It
  is now the union over every witness the grade stands on.
- The canonical invocation (2.1). The test searched the whole string for
  three flag substrings, so one canonical command vouched for a second
  with no flags, and extra options rode along. Each agda command must
  now be exactly the three flags and one module.
- +foundation-diverse (8.3). Any non-null value published the tag. It
  now needs an accepted, RECONCILED, receipted witness.

pwg-check.sh rejects a disposition outside c|b|debt and one recorded
for an axiom the receipt does not report.

Canaries 35-43. The ladder controls now record dispositions. Against
the pre-fix derivation six fail (35/41); against the pre-fix gate the
two disposition checks fail (41/43). The suite is 43/43.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01J4QvDim4mMEfCer9SiAV4H
- Veridicality Derivation: deceptiveDuals is a tuple value in both
  provers and states no proposition. It is no longer cited; the row says
  "exactly three" follows from the three uniqueness lemmas and the
  product construction, and is not one stated proposition.
- Verdict soundness: verdictSound is over a grade-shaped floor, as the
  source says. The row no longer writes it with the use-model floor,
  which is a different type with no connecting lemma.
- Tier-2 membership: names the ratified iff (GradeR.gradeR_leftCancel_iff)
  and marks Grade.grade_leftCancel_iff as the pre-ratification one.
- README: PROOF-STATUS and pwg.json do not "agree row for row"; the gate
  checks the grade table and census, not the hand-written prose rows.

grade-factorisation: the README verdict now says it is the
pre-ratification result and points at the ratified re-run, and lists
GradeFactorisationR.lean. REPORT's second axiom audit quoted the CI
allowlist as the result; the CI audit of both modules at 7b71c31 (run
43981767344, 184 declarations) reports propext and Quot.sound only.

No proof statement, token or grade changes.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01J4QvDim4mMEfCer9SiAV4H
@sonarqubecloud

Copy link
Copy Markdown

@github-actions

Copy link
Copy Markdown

Fork governance

Lane Status Run
DEED syntax (repo deed) 🟢 conformant run 44007724279
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 1cf45905e6f7 · run 44007724279 · 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 1cf45905e6f7 · run 44007724279 · scope: this change (11 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: 50 (50 reporter observations; 23 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 🟡 medium 0 0 2 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 10 — 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 27 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: 12 finding(s)
  • 12 further finding(s) in files this change does not touch: reported, not graded (0 critical, 0 high).
panic-attack assail: 3 finding(s)
  • medium CommandInjection — scripts/pwg-derive.sh — 118 potentially unquoted variable expansions in scripts/pwg-derive.sh
  • medium CommandInjection — scripts/pwg-check.sh — 35 potentially unquoted variable expansions in scripts/pwg-check.sh
  • 1 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 — verification/proofs/lean4/grade-factorisation/REPORT.adoc:1 — Line 97 characters exceeds max length of 80.
  • info VIS-005 — verification/proofs/lean4/grade-factorisation/README.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 85 characters exceeds max length of 80.
  • info VIS-005 — README.adoc:1 — Line 97 characters exceeds max length of 80.
  • 72 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): 126 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
  • ⚪ 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 04:33
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 829cae4 into claude/stripper-nesting-psibond Nov 17, 2026
41 checks passed
@hyperpolymath
hyperpolymath deleted the claude/gate-gaps-and-status-rows branch November 17, 2026 04:52
hyperpolymath pushed a commit that referenced this pull request Nov 17, 2026
…sibond

Brings in #122 (L4 in full and A2 proved in Agda, rechecked in Rocq and
core Lean), which merged into #119's branch after this branch had taken
#123. The merge is textually clean.

Checked on the merged tree, because #123 tightened what a grade may
stand on and #122 added receipts under the older rules:

  scripts/pwg-check.sh               PASS, table and census match
  scripts/pwg-derive.sh --census     PWG-3 15, PWG-2ii 7, ungraded 6 of 28
  scripts/test-gate-falsifiability   43/43
  tests/aspect_tests.sh              PASS

The census is the one #122 published. Its three new receipts report no
axioms, so the disposition rule admits them, and its Agda receipt
records the canonical invocation for both entrypoints.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01J4QvDim4mMEfCer9SiAV4H
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