State and Data Flows
Route authority, command, persistence, synchronization, and projection decisions.
HEAD a63778e| Read this page when | A change moves data between document state, interaction state, persistence, synchronization, or derived views. |
|---|---|
| First answer | Which state is authoritative, and which values are projections? |
| Boundary | This page routes state contracts; detailed authority, execution order, and persistence rules belong to the focused pages below. |
| Reading rule | Choose one focused contract below, then follow its source and verification links. |
| Follow-up | Open the matching authority, canonical-flow, or persistence page before reading implementation detail. |
The state model is split by decision so an Agent can load only the relevant contract:
| Decision | Contract |
|---|---|
| Which state is authoritative, and how do commands publish changes? | State authority and command boundaries |
| What is the canonical order of common state transitions? | Canonical state flows |
| How do restore, collaboration, residency, and CellPlane projection work? | Persistence, collaboration, and projection |
Use Ownership and dependency direction for layer boundaries and Domain reference for capability ownership. The pages above own the detailed state contracts; this page owns only the route between them.