Admissibility frontier · Edition 3

Expanded claim page · assertion 3 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 reason is practical. A little difference in imported root module, declaration selection, metadata removal, DAG sharing, reduction policy or transparency can change which cells are occupied and which declarations collide. The next useful act is not to imitate the infographic. It is to obtain the named files, data and pinned Lean/Lake environment, regenerate the census from a clean checkout, compile the 13 certificates with their axiom dependencies, and then measure which distinctions the fold retains or loses. Only after that does the proposed Hecke reading face its own separate operator-law test.

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

Scope

Chapter “The admissibility frontier”, section “the Lean fold now has a finite provenance gate”. This is assertion 3 of 3 in that section.

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

  1. Recover the declared objects and assumptions from the controlling documents.
  2. Check the calculation, construction, obstruction or stopping rule on those same objects.
  3. Compare the source conclusion with the exact assertion above; do not strengthen its verbs or enlarge its domain.
  4. 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