betrusted-ed25519-verified/verification
mrwulf 3bad795029 verification: pin the whole declaration surface (P1-b)
Phase 2b asks the kernel whether any AXIOM is declared under Proofs/. Phase 3
pins the cones of the named certificates. Between them sat every other
declaration in the corpus — around three thousand of them — and a helper lemma
quietly acquiring a hash oracle in its cone moved nothing either phase looked
at.

Phase 2c closes that. Ported from ltl-accumulator-verified, where a nine-attack
self-test proved a source-regex enumerator evadable by attributed, private,
indented and `instance` declarations and by a nested-namespace basename
collision. Reading the compiled environment sees what the kernel saw; no name
shape hides. Every constant contributes module, name, kind and full axiom cone,
and the observed set must equal inventory-allowlist.txt exactly in BOTH
directions, with a count trailer so a truncated run cannot pass as an empty
diff.

FOUR THINGS THIS BUILD GOT WRONG, each caught by a check rather than by review:

  - The number of inventory drivers is a per-repo FACT, not an assumption.
    dalek and anza cannot import their corpus as one environment (Proofs.Basic
    and Proofs.ConstSpecs both declare CurveFieldProofs.zero_spec); risc0 and
    betrusted have no Proofs.Basic at all. Determined by compiling a probe.
    check.sh now DISCOVERS its drivers from the filesystem instead of naming
    two, and the generator refuses to split out a module the repo lacks.

  - The split let one real declaration hide behind another's entry. Keyed on
    name alone, the two zero_specs produced byte-identical records, so 3022
    declarations were covered by 3021 allowlist entries. Caught by the count
    trailer. Every record now carries its originating module.

  - The gate's success line said "single sanctioned axiom", inherited from the
    accumulator's policy. This corpus permits NONE. A success message
    describing a different rule is how an assertion stops meaning anything.

  - selftest-axgate.sh lifted Phase 2b with a range ending at "Phase 3", so
    inserting Phase 2c between them made it swallow the new phase and die on
    variables only check.sh defines — surfacing as the BASELINE case failing,
    a self-test blaming a gate for its own extraction bug. Both self-tests now
    stop at the next phase marker whatever it is called, and refuse to run if
    they capture more than one phase. The guard is the fix; the range was the
    symptom.

WHAT THIS IS NOT, recorded in TRUSTED-BASE.md at the same length as the claim:

  - No independent cone walker. The accumulator cross-checks collectAxioms
    against a hand-written walker. Ported here it was wrong in BOTH directions
    on mathlib's inductive shapes: EdPoint gave [] against the kernel's three
    axioms, and once extended, ProjPoint gave three against the kernel's none.
    Two implementations disagreeing both ways are a second wrong answer, not a
    check. These cones rest on collectAxioms alone.

  - Thirteen Proofs/Scalar* modules are inventoried by nothing — the
    second-button seam, still open. Phase 2c names every uncovered module on
    every run so the omission is visible rather than inferred.

selftest-inventory.sh exercises the shipping gate with six cases, each
asserting a specific diagnostic, including the one that matters: a cone
widened by one oracle while name, module and kind stay put. Negative-tested by
disabling the gate's diff, which turns two cases red including one for the
wrong reason, correctly reported as such.

Verified green: 20 runs across the four repositories (four buttons, four
harness, four inventory, four axgate, four binding self-tests), zero red. The
four check-scalar.sh greens from the preceding sweep stand: that script neither
reads the pin file nor changed.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-30 01:20:20 +02:00
..
gen Coherence pass 4 (the closing pass): 4-tier apex documentation + hygiene 2026-07-06 04:01:19 +02:00
Proofs verification: pin the whole declaration surface (P1-b) 2026-07-30 01:20:20 +02:00
AUDIT-MANIFEST.txt verification: bind the statements, the specifications, and the model (P1-a) 2026-07-29 00:38:22 +02:00
check-scalar.sh Coherence pass 3: post-apex accuracy sweep, hygiene, guard ladder 2026-07-05 11:48:20 +02:00
check.sh verification: pin the whole declaration surface (P1-b) 2026-07-30 01:20:20 +02:00
CurveField.llbc PHASE 2 COMPLETE ON BETRUSTED: THE FULL POINT-LEVEL LIFT 2026-07-06 01:53:39 +02:00
CurveSig.llbc PHASE 2 COMPLETE ON BETRUSTED: THE FULL POINT-LEVEL LIFT 2026-07-06 01:53:39 +02:00
extract.sh PHASE 2 COMPLETE ON BETRUSTED: THE FULL POINT-LEVEL LIFT 2026-07-06 01:53:39 +02:00
GEN-MODEL.sha256 verification: bind the statements, the specifications, and the model (P1-a) 2026-07-29 00:38:22 +02:00
HARNESS.sha256 verification: pin the whole declaration surface (P1-b) 2026-07-30 01:20:20 +02:00
inventory-allowlist.txt verification: pin the whole declaration surface (P1-b) 2026-07-30 01:20:20 +02:00
inventory_gate.sh verification: pin the whole declaration surface (P1-b) 2026-07-30 01:20:20 +02:00
lean-guard Coherence pass 3: post-apex accuracy sweep, hygiene, guard ladder 2026-07-05 11:48:20 +02:00
selftest-axgate.sh verification: pin the whole declaration surface (P1-b) 2026-07-30 01:20:20 +02:00
selftest-harness.sh verification: pin the harness, the audit drivers and the policy files (P1-c) 2026-07-29 20:13:01 +02:00
selftest-inventory.sh verification: pin the whole declaration surface (P1-b) 2026-07-30 01:20:20 +02:00
selftest-statements.sh verification: pin the whole declaration surface (P1-b) 2026-07-30 01:20:20 +02:00