Authoritative design documents for over/ACP. Each doc here is the source of truth for one subsystem; if a doc and the code disagree, the doc is wrong and should be updated.
For the high-level architecture and milestone roadmap see
SPEC.md at the repo root.
protocol.md— wire protocol: WebSocket transport, JWT session claims, JSON-RPC method catalogue, shared payload types, schema-discipline rules, and the resolved naming policy. Theoveracp-protocolcrate is the Rust expression of this document.controlplane.md— superseded. Historical controlplane architecture:SessionStore,ComputeProvider, and the Kafka-Connect-shaped REST API for managing compute pools and agent lifecycle. Replaced by the stateless message broker model inSPEC.md. Kept for context only.context-management.md— how over/ACP separates the agent's working context from the operator's canonical conversation record. Covers auto-compaction, thecontext/compactednotification, agent-internal scaffolding, and the optional memory-flush hook.workspace-sync.md— pluggable workspace hydration and persistence: where it lives in the architecture (agent supervisor, not the broker), theWorkspaceSynctrait, the per-backend crate convention, and the configuration model.ha.md— multi-instance HA via Redis/Valkey: ownership leases, inbox streams, pub/sub SSE fan-out, and theredisfeature gate. Optional backend behindAgentRegistryProvider,MessageQueueProvider, andStreamBrokerProvidertraits.