The complete system map

Clients use authenticated HTTP for snapshots and query pages and WebSocket RPC for commands and live subscriptions. A serialized in-memory queue invokes a persistence- and provider-I/O-free decision layer that still reads the clock and creates UUIDs. That decision happens before events, SQL projections, and accepted receipts commit together. A hot PubSub then feeds best-effort reactors and live subscribers. Provider work routes through ProviderService, an instance registry, and one provider adapter before reaching the five native harnesses.

A client sends a typed command by WebSocket. The in-memory queue calls the decision layer before the SQL boundary, then atomically commits events, SQL projections, and an accepted receipt. After commit, a hot event bus independently feeds live subscribers and provider reactors. A reactor routes through ProviderService and an adapter to a harness. Canonical harness events return through runtime ingestion and re-enter the command queue. Separately, authenticated HTTP reads authoritative SQLite snapshots for initial and reconnect synchronization.