Rijad ZuzoArchitecture decisions
Decision records capture choices that should survive individual implementation plans. Use the next sequential number and include:
- context and problem;
- decision;
- consequences;
- staged migration, if needed;
- conditions for revisiting the decision.
Do not create records for routine edits or choices that are still exploratory.
Accepted records
| ADR | Scope | Current consequence |
|---|---|---|
| 0001 — simulation authority boundary | Fixed-step simulation, scene/presentation boundary, stable IDs, save authority | Loaded nodes may present and report geometry, but they do not own persistent facts or completion |
| 0002 — emergent world content and narrative | Typed packs, shared commands, causal facts, situations, dialogue, and one regional authority | New reusable content is data-first; new mechanics add bounded handlers; quests/dialogue project real world state |
The developer index summarizes how these decisions appear in the current modules. Add a new ADR only when a choice should survive multiple feature plans and has explicit revisit conditions.