Genesis: the strategic origin of the projection model
The insight behind this model did not arrive as a philosophical abstraction. It arrived as a collision between a specific strategic observation and the way I had been trained to think about systems.
In early 2026, during the escalating conflict between the US-Israel coalition and Iran, I was watching analysts discuss the strategic landscape. One analysis caught my attention: a United States aircraft carrier strike group had retreated 1,000 kilometers from its ideal launch position. The reasons given for this movement varied. The official claim cited a fire in the laundry. Speculative reports suggested a strike by Iranian forces. Other hypotheses remained open.
I come from software architecture, functional programming, event sourcing. I have spent years building systems where state is derived from events through pure functions. Watching that analysis, I saw not a narrative problem but a system state problem. The reason for the retreat was a matter of interpretation. The consequence of the distance was a matter of state.
A carrier positioned 1,000 kilometers further from its target is a carrier operating under different constraints. Its aircraft spend more range on transit, which means fuel tradeoffs, which means payload tradeoffs, which means reduced sortie options. The exact magnitude depends on aircraft type, tanker availability, mission profile. But the direction of the constraint is not narrative. Greater distance changes the state-space of possible operations.
That was the part that mattered to me. If the question is strike effectiveness under distance, then the cause of the movement can remain uncertain while the consequence can still be projected. A laundry fire, a kinetic strike, or an undisclosed operational decision may imply very different things about vulnerability, escalation risk, and adversary capability. Those are different projections answering different questions. But the distance-derived constraint on strike effectiveness is the same regardless of cause.
The discipline is to keep those projections separate.
The first formulation was simple:
State = Projection(Facts, Hypotheses)
If the state of a complex system is a deterministic projection of its facts and underlying hypotheses, then reasoning about that state can be treated with the same rigor as an event-sourced system. Identity persists, but state is derived. Information enters as an append-only ledger of facts, the system’s events. The current state is the replayed projection of those facts through governing rules, the pure functions of the domain.
The philosophical vocabulary came later. The instinct was architectural. I had been building systems like this for years. Isolating facts from interpretations, interpretations from projections. The geopolitical observation just showed me it applied beyond software.
The model eventually grew into nineteen primitives and eight epistemic layers. But its genesis remains the refusal to let the “why” of a movement obscure the deterministic “what” of its consequence.
This text was produced under the Canon Authoring Protocol. See 00-authoring-protocol.md, Author’s Declaration.