kernel-CReal.e
- Kind
- kernel-term
- Status
- checked
Supports: CReal.e is admitted by the trusted kernel gate as a definition with the type recorded in formal.statement.
cargo run -q --release -p axeyum-lean-kernel --example kernel_declaration_projection -- --require-declaration CReal.e --require-kind definition 2>/dev/null | grep -cE '^found[[:space:]]creal[[:space:]]definition[[:space:]]CReal\.e[[:space:]]' Evidence notes
DIRECT presence check, built this session (Task 1 of this batch): no in-tree example previously inventoried Declaration::Definition by name with fail-on-absence semantics (theorem_dependency_inventory / nat_theorem_inventory / prelude_theorem_inventory all filter to Declaration::Theorem and explicitly exclude Definitions -- 'Definitions, inductives and axioms are excluded' is theorem_dependency_inventory's own stated contract). Added '--require-declaration <name> [--require-kind <kind>]' to kernel_declaration_projection: it searches every constructed prelude's environment for an EXACT display-name match and exits non-zero when none is found, or when --require-kind is given and no match has that kind. Mutation-tested on an isolated /data0 snapshot (scripts/lane-snapshot.sh, never the shared checkout): renaming CReal.integral's display string to "integral_MUTATED" at crates/axeyum-lean-kernel/src/creal.rs:4389 made this exact check (run against CReal.integral) return count 0 / exit 1 in the rebuilt binary, while an unrelated control name (CReal.e) in the SAME rebuild still matched and exited 0 -- confirming the check discriminates on the intended declaration's own name, not on the build succeeding globally. --release is MANDATORY: this tool also builds creal/complex/cpoint, which overflow the default debug thread stack.