Impossible Simultaneity
Treating concurrent interpretations as if they could all be true at once
Invariants hold through controlled write authority — not by assuming conflicting states can coexist without commitment.
Two processes read the same state, draw different conclusions, and both write. The system allows it — or resolves it later through last-write-wins. For a brief or permanent window, contradictory facts coexist. Nobody committed to which interpretation governs; the infrastructure pretended simultaneity was coherent.
In software systems
The failure appears when multiple writers update shared mutable state without a single writer or reservation pattern. Two order services both see inventory of one unit and confirm separate orders. Two analysts update the same customer risk flag from different model runs; both values persist in different microservice caches. Eventual consistency promises convergence but the invariant — one seat, one sale — was violated in the interval, and possibly forever if reconciliation fails silently.
Distributed locks abandoned for availability leave the gap. CRDTs and merge strategies handle collaborative editing but are misapplied to domains requiring exclusive commitment: two approved credit limits for the same account, merged by max(). The architecture treats interpretation as simultaneously valid rather than forcing a commitment sequence. Read-your-writes consistency gives each writer confidence in their own view while the global record holds impossible superposition.
In human organisations
Two departments interpret the same contract clause differently and both act. Sales commits delivery dates; legal flags the commitment as unauthorised. Both emails are “official.” Finance recognises revenue; operations cannot fulfil. The organisation lacks a single writer for contractual interpretation — or a commitment ceremony to resolve conflict before action.
Matrix management amplifies the pattern. Product and engineering both believe they own prioritisation; both publish roadmaps. Neither record contains a superseding decision. Staff receive contradictory directives and execute against whichever arrived last in their inbox. The failure is not disagreement — disagreement is healthy. The failure is acting on conflicting interpretations without a commitment event that selects one authoritative reading.
In socio-technical systems
Clinical handoffs demonstrate compounded simultaneity. The ED physician documents “rule out MI”; the cardiology consult documents “NSTEMI likely.” Both entries appear active in the problem list without supersession. The pharmacy dispenses based on one; billing codes from the other. Nursing protocols conflict. Software permits multiple active diagnoses; organisational handoff norms discourage “overwriting” a colleague’s judgment; the patient experiences contradictory care paths until harm or lucky convergence.
The socio-technical stack treats parallel documentation as additive truth rather than requiring explicit commitment or supersession at the boundary. Each actor’s interpretation is preserved as fact; none is elevated to the governing decision for downstream action.
Structural causes
Diffuse write authority
When no single writer owns an interpretive or invariant domain, parallel mutation paths produce contradictory committed-looking state. Each writer’s local logic is sound; the global record is incoherent. Impossible simultaneity is the symptom of diffuse authority — not bad luck, but architecture that allowed multiple writers without a supersession or reservation discipline.
Epistemic tier collapse
L3 dashboards and combined views that mix streams of different vintages present a single authoritative picture without disclosing cross-stream consistency or epistemic uncertainty. Downstream actors treat the dashboard as L0-grade truth when it is high-uncertainty presentation — tier collapse at the read path, not training-time subjectivity.