Five Canonical Causal Relations

1. Setting

The light cone has a finite relation algebra in RS. Two events are timelike, spacelike, lightlike, past-boundary, or future-boundary related. The count is not arbitrary; it follows from D=3 and the ledger clock.

2. Equations

(E1)

$$ |\mathrm{CausalRelation}|=5 $$

Five causal relations.

3. Prediction or structural target

• causal relation count: predicted 5 (count); empirical Minkowski causal taxonomy. Source: RS light-cone module

This entry is one of the marquee derivations. The numerical or formal target is explicit, and the falsifier identifies the failure mode.

4. Formal anchor

The primary anchor is Physics.LightConeCausalityFromRS..lightConeCausalityCert.

def lightConeCausalityCert : LightConeCausalityCert where
  five_relations := causalRelation_count

end IndisputableMonolith.Physics.LightConeCausalityFromRS

5. What is inside the Lean module

Key theorems:

• causalRelation_count

Key definitions:

• CausalRelation
• LightConeCausalityCert
• lightConeCausalityCert

6. Derivation chain

• lightConeCausalityCert - Light-cone cert
• causalRelation_count - Causal relation count = 5

7. Falsifier

An internally consistent RS event relation outside these five categories refutes the finite causal relation certificate.

8. Where this derivation stops

Below this page the chain reduces to the RS forcing sequence: J-cost uniqueness, phi forcing, the eight-tick cycle, and the D=3 recognition substrate. If any upstream theorem changes, this page must be versioned rather than patched silently. The published URL is stable, but the version field is the contract.

9. Reading note

The minimal way to audit this page is to open the first Lean anchor and then walk the supporting declarations listed above. If the primary theorem is a module-level anchor, the key theorems section names the internal declarations that carry the mathematical load. This keeps the public derivation readable without severing it from the proof object.

10. Audit path

To audit light-cone-causality-five, start with the primary Lean anchor Physics.LightConeCausalityFromRS.lightConeCausalityCert. Then inspect the theorem names listed in the module-content section. The page is intentionally built so the public explanation is not a substitute for the proof object; it is a map into it. The mathematical dependency is the same in every case: reciprocal cost fixes J, J fixes the phi-ladder, the eight-tick cycle fixes the recognition clock, and the domain theorem listed above supplies the last step. If that last step is empirical, the falsifier section names what observation would break it. If that last step is formal, a Lean-checkable counterexample is the relevant failure mode.

11. Why this belongs in the derivations corpus

The corpus is organized around load-bearing consequences, not around file names. This entry is included because Physics.LightConeCausalityFromRS contributes a reusable theorem or definitional bridge that other pages can cite. Keeping the page public gives readers a stable URL, a JSON record, and a direct path into the Lean theorem page. If the entry becomes redundant with a stronger derivation later, the current slug should be retired rather than silently rewritten; the replacement should absorb its anchors and preserve the audit history.