AgentStateGraph

Agent state lives in context windows, scratch files and chat logs. None of it is branchable, none of it is attributable, and none of it survives the session that produced it.

Every state change is an atomic commit carrying the full provenance chain: what changed, the structured intent behind it, the reasoning, a confidence score, the acting agent, and the authority it acted under. That is what a git commit message tries to be — except structured, queryable, and enforced by the data model rather than by convention.

• O(1) branching and speculation — create, compare and discard branches instantly
• Schema-aware merge with CRDT-inspired conflict resolution
• Epochs — sealable, tamper-evident audit bundles with Merkle root verification
• Policy — authorization and cost-of-change gating via Cedar, Rego and WASM evaluators
• Taint and quarantine — mark sensitive paths, block writes, subscribe to changes
• Namespaces for ref-layer isolation in multi-tenant deployments
• Plans and tasks with a state machine, proofs and agent assignment

Rust core · 73 MCP tools · 8 language bindings · 4 storage backends · HTTP API

• Everything — it is the layer the rest of the suite writes to

Source-available under BSL-1.1, converting to Apache 2.0 18 months after each version's first publication. Internal use — including in production — is unrestricted.