Storage
Storage
Catalogue verified storage responsibilities and access patterns.
Status: Partial implementation reference — Code-confirmed; operational validation pending
Last reviewed: 2026-10-19
Scope
Stores, ownership, access paths, lifecycle and operational constraints where applicable. The source-confirmed baseline below covers part of this scope; remaining operational details are unknown.
Current implementation baseline
Corpus D1 is the content/history authority; R2 stores materialized event segments, public archive objects and private recovery payloads. D1 commit and verified archive coverage are separate states. Registration stores credentials, routing IDs and public identities in its own D1 database.
Events KV stores delivery progress; MCP KV stores OAuth records, and its Event Hub manages live connections. Response caches in Corpus and Resources hold replaceable public responses. A queue cursor or cache entry is not a corpus recovery boundary.
Evidence: Corpus schema, Registration schema, each Worker’s wrangler.jsonc, and Corpus persistence. See backup and restore before treating archives as backups.
