dalek-ed25519-verified/verification/Proofs/Inventory.lean
mrwulf 37bf01fc6f Account for every constant the kernel sees, by set containment
THE GAP. The capability matrix in the control repo — built after the author
answered a capability question by grepping for a FILENAME rather than for the
property, three times in one session — asked whether each repository's auditor
enumerates itself. The four ed25519 forks answered no. Following that up found
something larger: `Proofs/Audit.lean`, the statement-binding driver from P1-a,
is compiled, is a member of the manifest, and was enumerated by NOTHING. The
kernel counted 3058 declarations where the inventory accounted for 3022, and
26 of the 36 missing were its.

THE PROPERTY, now enforced: every constant the kernel sees under this button's
manifest must appear, BY NAME, in either the corpus inventory or the
instruments' own surface. `emitDrivers` in InventoryCore walks the audit
modules and fails closed on an axiom (which would widen the trusted base
outside every cone) or on a standalone claim (which no certificate covers and
no allowlist pins), while admitting the obligations the elaborator generates
for a definition declared alongside it.

TWO WRONG FORMULATIONS FIRST, both recorded because the second is instructive:

  · `kernel = corpus + instruments + N_DRIVERS`, where the last term was
    justified as a per-driver "self-observation blind spot". It fitted dalek
    and anza (2 drivers, residual 2) and broke on risc0 and betrusted
    (1 driver, residual 2). The residual is 2 everywhere and has nothing to do
    with drivers. This was curve-fitting from a sample of one, and it was named
    as the highest-risk claim in the round-7 self-assessment BEFORE the data
    refuted it.
  · distinct-by-name counting, which collapses `CurveFieldProofs.zero_spec` —
    a name that genuinely denotes two different declarations, in Proofs.Basic
    and Proofs.ConstSpecs, walked by two drivers with separate environments.

THE MEASURED CAUSE of the residual. Lean materialises equation lemmas lazily,
when something forces an unfold, and each module that forces one gets its own
copy in its object file. `CurveFieldProofs.denote.eq_1` sits in both
SubNegSpec.olean and ConstSpecs.olean; `CurveFieldProofs.limbsVal.eq_1` in both
ReduceSpec.olean and ConstSpecs.olean. The kernel gate reads object files and
counts both copies; the environment holds one constant per name. Counts cannot
relate those two views in either direction — so the check compares SETS, which
is the idiom the rest of this estate already uses, and no constant remains that
could be widened to make a red run green.

Negative-tested: with the instrument walk disabled, the check names
Proofs.Audit's declarations as unaccounted.

ANZA also lacked one allowlist row, `subtle.Choice...from.eq_1`, the same
lazy-materialisation effect seen from the other side. Verified rather than
assumed before adding it: the parent is declared in gen/CurveField/
FunsExternal.lean — the model, pinned by bytes and not inventoried by
declaration — the lemma materialised in Proofs.CompressSpec which forced the
unfold, and all three other forks carry the lemma row while none carries the
parent.

CONSEQUENCE WORTH DISCLOSING: the audited declaration surface is not purely a
function of the corpus source. It depends on which proofs forced which
unfolds. This is now a known gap in the round-7 kit.

Also corrected here: Proofs/Inventory.lean's header claimed the audit drivers
were excluded from the compile manifest. They are lines 42-44 of PROOFS.

Certified by a full sweep: both buttons, all four forks, purged trees. 8/8.
2026-08-01 16:10:59 +02:00

90 lines
4.2 KiB
Text

/- ──────────────────────────────────────────────────────────────────────────
Proofs/Inventory.lean — environment-derived declaration inventory (main chain).
Audit INFRASTRUCTURE, not corpus. It proves nothing and is imported by
nothing. It IS a member of check.sh's compile manifest — lines 42-44 of
PROOFS — so Phase 2b's kernel-side gate reads its `.olean` and an axiom
declared here is rejected. (An earlier version of this comment claimed the
drivers were excluded from the manifest. That was false, and the capability
matrix in the control repo found it on 2026-07-31.)
Its constants are outside the corpus walk below, and are emitted separately
by `emitDrivers` as DRV rows: the kernel counted 3058 declarations where the
inventory accounted for 3022, and those 36 are this machinery. check.sh now
requires the two walks to account for the kernel's count exactly.
Covers every module check.sh compiles except any listed as needing a
separate driver (see Proofs/InventoryBasic.lean if present). Whether
a split is needed was determined by compiling a probe, per repo.
────────────────────────────────────────────────────────────────────────── -/
import Proofs.InventoryCore
import Proofs.Audit
import Proofs.Denote
import Proofs.P25519
import Proofs.ReduceSpec
import Proofs.SubNegSpec
import Proofs.ConstSpecs
import Proofs.AddSpec
import Proofs.MulSpec
import Proofs.SquareSpec
import Proofs.Square2Spec
import Proofs.Field
import Proofs.InvertSpec
import Proofs.FieldMain
import Proofs.FeQ
import Proofs.EdCurve
import Proofs.EdDenote
import Proofs.EdDouble
import Proofs.EdAddProjNiels
import Proofs.EdAddAffNiels
import Proofs.EdConvert
import Proofs.EdMain
import Proofs.DsmTableSpec
import Proofs.DsmStepSpec
import Proofs.DsmLoopSpec
import Proofs.DsmNafLoadSpec
import Proofs.DsmNafMath
import Proofs.DsmNafLoopSpec
import Proofs.DsmNafSpec
import Proofs.DsmMulSpec
import Proofs.ToBytesMath
import Proofs.ToBytesSpec
import Proofs.CompressSpec
import Proofs.ScalarPackSpec
import Proofs.SigApexSpec
import Proofs.PointLiftSpec
import Proofs.PointEqSpec
import Proofs.DecompressSpec
import Proofs.FromBytesSpec
import Proofs.DecompressMain
open Lean Ed25519Inventory
/-- Exactly the modules this driver covers. check.sh verifies, in BOTH
directions, that the union of the two drivers' lists is its PROOFS
manifest minus the audit infrastructure. -/
def corpus : Array Name :=
#[`Proofs.Denote, `Proofs.P25519, `Proofs.ReduceSpec, `Proofs.SubNegSpec,
`Proofs.ConstSpecs, `Proofs.AddSpec, `Proofs.MulSpec,
`Proofs.SquareSpec, `Proofs.Square2Spec, `Proofs.Field,
`Proofs.InvertSpec, `Proofs.FieldMain, `Proofs.FeQ, `Proofs.EdCurve,
`Proofs.EdDenote, `Proofs.EdDouble, `Proofs.EdAddProjNiels,
`Proofs.EdAddAffNiels, `Proofs.EdConvert, `Proofs.EdMain,
`Proofs.DsmTableSpec, `Proofs.DsmStepSpec, `Proofs.DsmLoopSpec,
`Proofs.DsmNafLoadSpec, `Proofs.DsmNafMath, `Proofs.DsmNafLoopSpec,
`Proofs.DsmNafSpec, `Proofs.DsmMulSpec, `Proofs.ToBytesMath,
`Proofs.ToBytesSpec, `Proofs.CompressSpec, `Proofs.ScalarPackSpec,
`Proofs.SigApexSpec, `Proofs.PointLiftSpec, `Proofs.PointEqSpec,
`Proofs.DecompressSpec, `Proofs.FromBytesSpec, `Proofs.DecompressMain]
/-- The instruments. `Proofs.Audit` is the statement-binding driver: it is a
member of check.sh's compile manifest and it was enumerated by NOTHING —
26 of the 39 declarations the accounting identity found missing were its.
`Proofs.InventoryBasic` is reachable by module index only
if this driver imports it; it does not, so it emits its own DRV rows under
its own run and check.sh sums the two. This module has no index while it is
being elaborated, so `emitDrivers` picks its declarations up as the ones the
environment reports with no originating module. -/
def drivers : Array Name := #[`Proofs.InventoryCore, `Proofs.Audit]
#eval show MetaM Unit from emitInventory corpus
#eval show MetaM Unit from emitDrivers drivers