Architecture
Event-driven memory architecture
How stable records, ordered history, deterministic computation, and event-driven recovery support long-running agents.
Why it helps
Simple primitives make correctness and bounded work easier to prove.
Stable records and ordered history
Each record has a stable ID and revision. Ordered history stores references to those exact records, so a correction can create a new version without rewriting an older published view.
Deterministic Rust reducer
Cloud I/O and scheduling are separated from deterministic computation. The reducer turns accepted history into maintained trajectory state that can be compared with an independent full-recompute oracle.
Event-driven maintenance
Durable work, queue wakeups, bounded continuation, scheduled maintenance, and recovery keep state converged without requiring an LLM to rebuild history.