One-sentence brief
A current-state snapshot shows what the system believes now; an event history explains how it got there and which corrections must propagate.
SIMULATION LITERACY
How append-only event history, snapshots, replay, and labeled branches can support reproducibility, correction, and counterfactual comparison.
ORIENTATION
A current-state snapshot shows what the system believes now; an event history explains how it got there and which corrections must propagate.
WORKING BRIEF
An event should describe the previous state, transition, new state, responsible rule or authority, timestamp, source references, and model version.
Appending rather than overwriting preserves audit and correction history. Corrections can be represented as new events that supersede or reverse earlier state.
A snapshot accelerates loading by recording derived state at a point in time. It should include the event position and digest needed to verify reconstruction.
Replay reconstructs state under the same rules and inputs. Reproducibility depends on deterministic order, versioned logic, and controlled randomness.
A branch creates a counterfactual timeline from a known point. It should have its own identity, assumptions, and output store.
Auditability should not become indefinite surveillance. Retention, access, correction, privacy, and deletion rules must be proportionate to purpose.
COMPLETE DOSSIER
Terms are defined for this site’s evidence method, not as universal legal or clinical definitions.
RESEARCH EDITION
This page follows the public method for provenance, confidence, source independence, alternative accounts, limitations, review state, and visible correction.
CONTINUE