Firestore data reference

Tenant paths are constructed by src/lib/tenancy.ts. Workspace membership is resolved before tenant-scoped reads or writes.

Record family	Purpose
`workspaces`, `members`, `brands`	Tenant identity, membership, and brand context
`jobs`, events, stage outbox, stage executions	Workflow state, history, delivery, and claims
strategy and editorial-plan fields on jobs	Versioned proposals, digests, approvals, and lineage
`pending_operations`, `chat_runs`, `chat_attachments`	Conversational commands, streams, and uploads
`content_items`, `effect_commands`	Calendar items and digest-bound execution commands
approvals, claims, receipts, verifications	Human authority and effect evidence chain
usage, budgets, notifications	Cost controls and operator attention

Binary media belongs in the asset store; Firestore records identifiers, URIs, digests, rights, and lineage. Pub/Sub delivers triggers, while Firestore transactions decide whether a trigger is current and claimable. See State ownership.

Integration reference

Workflow contracts

Evidence

Firestore data reference