Concepts
Second-pass vocabulary for the deterministic domain runtime.
If you are still trying to get the first app running, go back to Quick Start and Tutorial. This section is for when the app path mostly makes sense and you want the vocabulary to click.
Core Concepts
| Concept | Definition | Key Principle |
|---|---|---|
| Shared Domain Model | One domain, many surfaces | Define once, call from UI, routes, and agents |
| Snapshot | Default runtime read model | Read snapshot() first; use full internal snapshots only for advanced tooling |
| Intent | Low-level request behind an action submission | App code submits actions, tooling may inspect intents |
| Flow | Declarative computation as data | Flows describe, they do not execute |
| Effect | Declaration of external operation | Core declares, Host fulfills |
Optional Extension Concepts
| Concept | Definition | Read When |
|---|---|---|
| Lineage Records | Lineage-owned immutable records for stored full Snapshots | You need history, restore, audit, or approval/history runtime details |
Base And Extensions
| Path | Use It When |
|---|---|
| Base runtime | You want direct action submission through createManifesto() -> activate() |
| Optional extension runtime | You need review, branch history, audit, restore, or sealed records on top of the same domain model |
The Fundamental Equation
compute(schema, snapshot, intent, context) -> ComputeResult- Pure: Same inputs always produce same outputs
- Total: Always returns a result
- Traceable: Every step is recorded
- Complete at the internal boundary: the runtime has the full state it needs; SDK
snapshot()is the default app read model
See Also
- Quick Start for the runnable path
- Tutorial for the learning path
- When You Need Approval or History before reading Lineage records
- Architecture for the system-level picture
- Internals for specs and historical decisions