PC-0002: The Architecture of Causal Systems — Data Layer

Question

Executive Summary

PC-0002 defines a structural transition from state-based reasoning systems to causal reconstruction systems.

In this model, system truth is not represented as a mutable snapshot (state), but as an append-only sequence of immutable events from which state is deterministically derived.

• State is not truth
• Events are truth primitives
• Causality is reconstruction

---

1. Core Structural Decomposition (MECE Model)

The system is defined across four mutually exclusive primitives.

A. State (Derived Artifact)

• Definition: A computed snapshot representing system conditions at a specific time t=n.
• Properties: Transient, Incomplete, Overwritten over time, Lossy compression of event history.
• Catalog Role: State is non-authoritative. It is a derived convenience, not a source of truth.

B. Event (Primary Truth Unit)

• Definition: An immutable record of occurrence with timestamped conditions.
• Properties: Append-only, Non-destructive, Time-anchored, Fully reconstructable.
• Catalog Role: Events are the irreducible primitives of system truth.

C. Causality (Relationship Layer)

• Definition: A deterministic mapping that explains system evolution through event relationships.
• Core Transformation: state = fold(events)
• Properties: Deterministic replay, Dependency-aware reconstruction, Time as structural dimension (not contextual variable).

D. Ledger (Persistence Model)

• Definition: An append-only storage system for event history.
• Constraints: No overwrite, No deletion, Full audit traceability, Deterministic replay required.
• Catalog Role: The ledger is the system’s memory substrate.

---

2. Execution Model (Causal Pipeline)

The system operates as a strict transformation chain:

1. Event Stream (immutable facts)
2. ↓
3. Ledger (append-only history store)
4. ↓
5. Causal Fold Function (pure transformation)
6. ↓
7. Derived State (computed truth projection)

Each stage is deterministic and non-overlapping.

---

3. Core Principle: Reversal of Authority

Traditional systems assume: State → Truth

PC-0002 enforces: Events → Truth → Derived State

This inversion removes ambiguity introduced by snapshot-based reasoning. The system does not ask “what is true now?” It computes “what must be true given what happened.”

---

4. Failure Mode Analysis

4.1 Shared Mutable State Systems Fail Because:

• Race conditions create divergent outcomes.
• Concurrent writes overwrite historical truth.
• Snapshots diverge from actual system history.
• Reproducibility is lost under concurrency.

4.2 Causal Systems Succeed Because:

• History is append-only.
• Execution is replayable.
• Events are immutable.
• State is always reconstructable.

Every failure becomes a traceable sequence, not a hidden defect.

---

5. MECE Structural Guarantees

Layer	Role	Constraint Behavior
Event	Atomic truth unit	Immutable, no mutation
Ledger	Historical storage	Append-only, no deletes
Causality	Relationship logic	Pure function, no side effects
State	Derived output	Non-authoritative

Each layer is:

• Mutually exclusive in responsibility.
• Collectively exhaustive in coverage.

---

Machine Metadata

{
  "id": "PC-0002",
  "title": "The Architecture of Causal Systems",
  "layer": "data",
  "graph_role": "intermediate",
  "depends_on": ["PC-0001"],
  "edges_to": ["PC-0003"],
  "state": "published",
  "truth_anchor": "DOI 10.5281/zenodo.18894084"
}

---

Closing Doctrine

A system that cannot reconstruct its own history cannot reason about its own truth.

Event-driven architecture is not a performance model. It is a commitment to causality as the foundation of correctness.

• If events are preserved, truth is reconstructable.
• If events are lost, reality becomes speculative.