Scope
Chapter “The admissibility frontier”, section “the Lean fold now has a finite provenance gate”. This is assertion 1 of 3 in that section.
Expanded claim page · assertion 1 of 3
the Lean fold now has a finite provenance gate
Ledger / governanceAuditor
Preserves provenance, status, stopping rules and navigation. checks assumptions, certificates, counterexamples and stopping rules.
Exact assertion
The public images behind the reported Monster-address census name the missing implementation artifacts: three `RequestProject/Ogg/DeclFold*.lean` files, the generated `fold/decls.json`, the `fold_certify` command and the worked declaration `HeckeFold.card_address`. This turns a vague request for “the code” into a finite reproduction bundle.
What this commits us to
The claim organizes provenance, scope or stopping rules. It governs how evidence is read rather than adding independent physical evidence.
Logical anatomy
Evidence posture
Use this passage to inspect provenance, scope and stopping rules rather than as independent physical evidence.
Research move
checks assumptions, certificates, counterexamples and stopping rules.
Verification route
- Recover the declared objects and assumptions from the controlling documents.
- Check the calculation, construction, obstruction or stopping rule on those same objects.
- Compare the source conclusion with the exact assertion above; do not strengthen its verbs or enlarge its domain.
- Apply the status rule and retain every named external dependency.
What would move or defeat this claim
Find a provenance mismatch, stale status, broken link or stronger source that changes the ledger entry.
Source map
Controlling documents
- admissibility 60 monster lean fold provenance and reproduction gateOpen controlling document →
- frontier wave7 30 kernel closure and expression tree reachability sieveOpen controlling document →
- frontier wave7 35 adaptive depth census and detector cost curveOpen controlling document →