Complex conjugation is additive

Identifier: F:complex-conj-add
Proof route: kernel-lean
External status: proved
Axiom footprint: Empty

Recorded description

For all constructed complex numbers a and b, conj(a + b) is Complex.Equiv-equivalent to conj(a) + conj(b) -- conjugation is a ring homomorphism on the additive structure.

Formal statement

theorem Complex.conj_add : ((x0 : Complex) -> ((x1 : Complex) -> Complex.Equiv (Complex.conj (Complex.add x0 x1)) (Complex.add (Complex.conj x0) (Complex.conj x1))))

Dependencies

The graph shows direct ledger edges. Follow a node to open its artifact page.

9 direct dependencies 0 direct dependents Graph shows the first 8 on each side.

Evidence

kernel-Complex.conj_add

Kind: kernel-term
Status: checked

Supports: Complex.conj_add is admitted by the trusted kernel gate with the type recorded in formal.statement.

Checker command

cargo run -q --release -p axeyum-lean-kernel --example theorem_dependency_inventory -- Complex.conj_add 2>/dev/null | grep -cE '^Complex\.conj_add[[:space:]]'

Evidence notes

`build_complex_prelude` admits Complex.conj_add through the trusted `Kernel::add_declaration` gate, which re-checks the proof term against the stated type, so a line in this tool's output for the exact name is a machine-checked proof having been admitted. `theorem_dependency_inventory` builds creal/complex/cpoint (extended 2026-08-25); it exits non-zero for a named filter that matches nothing, and `grep -c` (never `-q`) independently asserts the exact tab-anchored line is present. `--release` is MANDATORY: building the constructed carriers recurses deep enough in a debug build to overflow the default thread stack (measured on this tree: release exits 0, debug SIGABRTs at 134) -- the same resource-limit gotcha documented for `prelude_theorem_inventory --include-constructed`.

footprint-Complex.conj_add

Kind: exhaustive-enumeration
Status: checked

Supports: axiom_footprint: [] -- the Complex prelude's trusted surface is empty

Checker command

cargo run -q --release -p axeyum-lean-kernel --example nat_axiom_inventory -- --include-constructed --require-axiom-free complex

Evidence notes

`nat_axiom_inventory --include-constructed` builds the Complex environment as its own group and reports `complex: axiom=0 opaque=0 quotient=0 total_trusted=0` (re-measured on this tree). That bounds every individual Complex theorem's footprint by [], since a theorem cannot depend on a trusted declaration the environment does not contain, and the enumeration covers Axiom, Opaque AND Quotient, not just Declaration::Axiom. `--include-constructed` is REQUIRED here -- without it `--require-axiom-free complex` is an error (verified: exit 1, '"complex" is not enumerated by this run'), not a silent pass, because complex is not built at all without the flag; this is the standing trap of an empty/absent result reading as a strong negative when the tool was never pointed at the subject.

Provenance

{
  "date": "2026-08-25",
  "established_by": "axeyum-lean-kernel build_complex_prelude",
  "source": "theorem name and dependency edges from theorem_dependency_inventory (builds creal/complex/cpoint); canonical type read via a standalone probe binary depending on axeyum-lean-kernel by path, calling only its public Kernel API (environment(), display_name(), render_lean(), axiom_footprint()) -- no in-tree example prints Complex/CPoint theorem types; crates/ source was not touched to produce this batch."
}