Lockstep Digital Twin

This proof builds the stricter version of the claim. Each accepted action is projected into the twin and sent against a mocked live Dynamics instance. Execution halts the moment the two disagree.

Operating rule: a digital twin only counts while the simulated state and the live state remain in lockstep. Drift is a failure condition, not a cosmetic detail.

Each action carries a twin projection and a live adapter response.
Small state can be embedded while large evidence stays referenced or derived.
Hashes and field-level diffs decide whether the twin is still valid.
The console can step one action at a time or sprint until drift.