How Kaizen works | Kamiwaza Docs

📄️Architecture at a glance

Three nested views — context, services, and inside the backend.

Every process in the topology, what it owns, and what it deliberately does not.

One non-generative round trip, from query expansion to ranked cards.

The backend-runtime callback loop, step by step, with the guard at each hop.

Two surfaces over one authorized matching pipeline, and when to use each.

Lexical and vector branches, the trusted SQL boundary, fusion, and reranking.

Runtime discovery, per-member identity, sync, and freshness.

The conversational loop, its authority bundle, and how it survives failure.

The registry, capability ceilings, parallel calls, and the write guard.

Routing to Kamiwaza, policy, budgets, effort, retries, and response normalization.

Delegation as a bounded tool call, and the limits it inherits.

Deployment-selected isolation, the lease pool, controlled egress, and per-participant workspaces.

The append-only journal, the turns cache, reconnect, replay, and terminal outcomes.

Definition, occurrence, run, and trace — and how work is claimed exactly once.

Always-on system compaction versus the opt-in member compression seams.

What lives in Postgres, Valkey, and the object store, and who owns each record.

The agent-to-agent proof of concept and why an Agent Card grants nothing.