Establish completeness of Lean’s axiom-reporting mechanism

Establish whether Lean 4’s `#print axioms` and `collectAxioms` mechanisms completely report all axioms reached through imported inductive types, thereby determining whether their axiom-dependency reports are complete rather than under-reporting dependencies.

Background

The paper audits the axioms reached by the Blanc verification library through an independent dependency walk rather than relying solely on Lean’s #print axioms command. The authors report an existing Lean issue concerning cases in which imported inductive types can cause the standard axiom report to under-report dependencies.

The unresolved problem concerns the completeness of Lean’s axiom-reporting infrastructure, not the soundness of Lean’s kernel. Resolving it would clarify whether conventional axiom reports can reliably certify the trusted base of formal developments involving imported inductive types.

References

We do not rely on Lean's #print axioms, which can under-report axioms reached through imported inductive types, an open issue we reported [lean4#15226] that concerns the completeness of that report, not the soundness of the kernel.

— Verifying deployed bytecode against executable EVM semantics, with exact gas and no added axioms  (2610.19764 - Baek, 14 Oct 2026) in Section 3.11, “What the kernel checks, and what it does not”