kernel-Complex.polyMul
- Kind
- kernel-term
- Status
- checked
Supports: Complex.polyMul is admitted by the trusted kernel gate with the type recorded in formal.statement.
cargo run -q --release -p axeyum-lean-kernel --example kernel_declaration_projection -- --require-declaration Complex.polyMul --require-kind definition 2>/dev/null | grep -cE '^found[[:space:]]complex[[:space:]]definition[[:space:]]Complex\.polyMul[[:space:]]' Evidence notes
Complex.polyMul is a Declaration::Definition. theorem_dependency_inventory / nat_theorem_inventory / prelude_theorem_inventory all filter to Declaration::Theorem and exclude Definitions, so this fact uses the DIRECT 'kernel_declaration_projection --require-declaration' checker (added earlier in this session's batch): it searches every constructed prelude's environment for an exact display-name match and exits non-zero on no match or kind mismatch. Verified on this tree: the command prints exactly one 'found\tcomplex\tdefinition\tComplex.polyMul\t...' line (a definition built this early in the dependency order also shows up, separately, under the downstream complex/cpoint preludes that rebuild Complex from scratch as their own Kernel instance -- this checker deliberately anchors on the complex row only, the prelude Complex.polyMul is native to). --release is MANDATORY: this tool also builds creal/complex/cpoint, which overflow the default debug thread stack.