How to read a simulation
Treat each fork as a comparable experiment. Scan the snapshot first, then drill into deltas and drivers.
CONTINIUMGUIDES
Simulation guides
Practical reading notes for Continium outputs: how to scan, compare, and extract decisions from artifacts.
READING ORDER
1) Snapshot (what changed?)
2) Deltas (where did it move?)
3) Drivers (why did it move?)
4) Assumptions (what must be true?)
Decision quality comes from inspectable drivers.Start broad, then narrow: outcome -> delta -> driver -> assumption.
PLAYBOOK
How to ask better questions
Ask for decisions, constraints, and a horizon. Make assumptions explicit so outputs stay inspectable.
How to compare forks
Compare outcomes side by side, then attribute differences to drivers instead of vibes. Look for stable deltas across time.
NEXT
Want the definitions behind the words?
Use the glossary to keep forks, deltas, drivers, and artifacts consistent.