CutCptCopy source audit
November 20, 2026 · Published Lean 4.33.1 source
CutCptCopy.lean adapts existing proofs to compact-support hypotheses. It changes the statement and proof together, then passes the new declaration to Lean for checking. Both branches submit a definition or theorem with a body. Neither branch creates an axiom or requests a kernel bypass. Inspect the two declaration types it accepts.
What the command changes
- It starts from six named declarations and follows constants in their types and bodies within the
Formalismnamespace. It tracks which declarations depend on the replacements. Read the starting names and traversal. - It maps three constants to specific compact-support replacements. Fourteen other names have explicitly supplied counterparts ending in
Cpt. Inspect the substitution lists. - For each affected definition or theorem, it rewrites constant references in both the type and the body. It submits the result through
addDecl. A replacement still has to type-check when used in the rewritten proof. Inspect substitution and registration.
Where the adapted result is used
CutGermDone proves a block-growth estimate under ThmPActual. In FinalS, a theorem takes the compact-support hypothesis ThmPActualCpt and calls block_growth_bound_of_compact_coefCpt. This is a concrete use of the compact counterpart of the third starting declaration. Original estimate · Downstream use
Why the suffix can be misleading
The command skips a destination name if it already exists. For example, CutMainCpt.lean explicitly proves thmBpAt_main4Cpt at line 475. The file invokes the copier at line 945. The command logs how many declarations it added, without listing their names. Skip condition · Explicit proof · Invocation
What remains open
The archive’s import index places the copier 17 imports below Main on its shortest path. A clean build of Main therefore includes the module that invokes it. Establishing which generated declarations the final RH proof actually depends on requires inspecting the compiled proof terms. The independent review checks the submitted theorems against separately stated targets, audits their axioms and replays the proofs. A passing replay would establish the stated theorems under the reported axioms. Identifying individual generated dependencies requires a trace of the compiled terms. Read the independent review results.