Foundation Dalembert Triangulated Proof Additive Not Entangling

The additive combiner

The additive combiner is a rule for combining two costs into one. If the cost of the first event is u and the cost of the second is v, the additive combiner returns u + v. This is the most natural way to combine costs: the total cost is just the sum of the parts. The framework's machine-checked library of formal theorems proves a fact about this combiner: it is not entangling. Entangling, in this context, means that the combined cost contains a cross term, a term proportional to u times v, so that the total is not simply the sum of the parts. The additive combiner has no such cross term, by definition.

The theorem additive_not_entangling states this formally: the additive combiner is not entangling. This is a proved theorem, not a hypothesis. The proof is in the framework's library, in the module that builds a triangulated proof of inevitability. The theorem is a small piece of a larger argument. The larger argument distinguishes two possible cost functions. One is the framework's preferred cost, called J, which has a hyperbolic structure. The other is a flat counterexample, called Fquad. The additive combiner belongs to the flat branch. The framework proves that the additive combiner is not entangling, while the preferred combiner, called RCL, is entangling. This contrast is one of four gates that the framework uses to separate the two branches.

The theorem does not claim that the additive combiner is impossible or forbidden. It merely establishes a property, or rather the absence of a property. The additive combiner exists and is a perfectly coherent rule. The framework's point is that it is not the rule that emerges from the forcing chain. The chain of proofs that leads to the unique cost function J also leads to the RCL combiner, not the additive one. The additive combiner is a useful contrast case, a flat alternative that fails the tests that J passes.

What the theorem does not claim is broader than what it does claim. It does not say that the additive combiner is inconsistent or that it leads to a contradiction. It does not say that the additive combiner is never used in practice. It does not say that entanglement is a good thing or a bad thing in general. It simply records a mathematical fact: the additive combiner lacks a cross term, and therefore it is not entangling. This fact is one small piece of evidence in the framework's larger argument that a specific cost function and a specific combiner are forced by the structural axioms.

/-- Additive combiner is not entangling. -/
theorem additive_not_entangling : ¬ IsEntangling Padd := Padd_not_entangling

/-- **Summary Theorem**: All four gates point to the same conclusion.

    - Gate 1 (Interaction): Distinguishes J from Fquad
    - Gate 2 (Entanglement): Characterizes RCL vs additive combiner
    - Gate 3 (Curvature): Characterizes hyperbolic vs flat ODE
    - Gate 4 (d'Alembert): Forces λ = 1 in cosh(λt), completing the chain

    All four gates are consistent: J passes all four, Fquad fails all four.
-/
theorem gates_consistent :
    -- J has all four properties
    HasInteraction Cost.Jcost ∧
    IsEntangling Prcl ∧
    SatisfiesHyperbolicODE Gcosh ∧
    FourthGate.HasDAlembert Cost.Jcost ∧
    -- Fquad/Padd have the opposite properties
    ¬ HasInteraction Counterexamples.Fquad ∧
    ¬ IsEntangling Padd ∧
    SatisfiesFlatODE Gquad ∧
    ¬ FourthGate.HasDAlembert Counterexamples.Fquad := by
  exact ⟨Jcost_hasInteraction, Prcl_entangling, Gcosh_satisfies_hyperbolic,
         FourthGate.Jcost_has_dAlembert_structure,
         Fquad_noInteraction, Padd_not_entangling, Gquad_satisfies_flat,
         FourthGate.Fquad_not_dAlembert_structure⟩

What this page does not claim

The additive combiner is inconsistent or leads to a contradiction. The additive combiner is never used in any practical context. Entanglement is inherently desirable or undesirable outside the framework's specific argument.

Verify this page

Every tagged claim above names its theorem. To check one yourself rather than trust this page, elaborate the source module with Lean 4 and audit its axiom basis:

$ lake env lean IndisputableMonolith/Foundation/DAlembert/TriangulatedProof.lean
expected axiom basis: [propext, Classical.choice, Quot.sound] (the Lean kernel's standard three; no RS-specific axioms)

A page whose claims cannot be reproduced this way does not ship. In production, every anchor links to the exact declaration in the public source release, and this block carries the build receipt for the page itself.

Derived articles

This page is generated by a question-recursion engine: the questions its answers raise become the next pages. The current agenda, with open targets marked red: