This is the developer-level operator guide for Echo. Use it for orientation, the productive-fast path, and to understand how the simulation engine orchestrates the causal graph.
For deep-track doctrine, theoretical foundations (AION Foundations), and internal spec details, use ADVANCED_GUIDE.md.
Integrate deterministic graph rewriting into your application or game.
- Read: Start Here
- Host: Architecture (Engine pipeline)
Use the "Drill Sergeant" discipline to prove cross-platform convergence.
- Read: DIND Harness
- Run:
cargo xtask dind run
Explore the worldline algebra through the interactive debugger.
- WASM: ttd-browser
- Host: echo-ttd
Understand the guardrails that prevent non-determinism from entering main.
- Check:
det-policy.yaml - Scripts:
scripts/ban-nondeterminism.sh
Echo is a tiered engine. You choose your depth based on the task:
- Ingress Surfaces (Surfaces): The CLI, WASM guest, and App Core are thin interfaces that communicate with the engine. They ensure that transitions are always structured.
- warp-core (The Engine): The primary domain kernel. It orchestrates parallel rule execution, private deltas, and canonical merge. It ensures that concurrency is structurally prevented.
- WARP (Memory): The Structural Worldline Memory that tracks the evolution of your simulation state through hash-locked ticks.
- I am setting up the repo: Run
make hooksandcargo check. - I am writing a new rule: Declare your
Footprintand test againstdelta_validate. - I am debugging a desync: Run
cargo xtask dind run --seed <N>to reproduce. - I am contributing to Echo: Read
METHOD.mdanddocs/BEARING.md.
If you need a comprehensive spec, use the docs/index.md map.
If you need to know "what's true right now," use docs/BEARING.md.
If you are just starting, use the README.md and the orientation tracks above.
The goal is inevitability. Every state transition is a provable consequence of its causal history.