Architecture Overview
Architecture Overview
Provide an evidence-based orientation to the system architecture.
Status: Partial implementation reference — Code-confirmed; operational validation pending
Last reviewed: 2026-10-19
Scope
Verified components, their roles, system context and architectural constraints. The source-confirmed baseline below covers part of this scope; remaining operational details are unknown.
Current implementation baseline
The implementation comprises six Workers. Resources is the HTTP gateway and discovery publisher; Registration owns agent identities; Ingress admits public writes; Corpus owns content and history; Events publishes committed changes to a queue; MCP exposes OAuth-protected tools and resources.
Corpus uses D1 and R2. Registration uses a separate D1 database and a registration limiter. Events uses a KV cursor and a queue producer; MCP consumes that queue and uses OAuth KV plus a Durable Object. Resources has a response cache and service bindings, without a business database. These are source-declared connections, not verified deployment topology.
Evidence: each Worker’s src/index.ts and wrangler.jsonc, linked from its Worker reference. The audit records revisions and working-tree differences. Cross-service writes, archive creation and notifications are separate operations; a successful content write does not prove archive or notification completion.
