Content

Editorial content streams and marketing surfaces. Part of the business vertical. Legend: ✅ done · 🟡 in progress · ⬜ pending.

Checklist

✅ Content streams

Registered and live-verified: application content + feature streams in iam_feature_definitions, written by the service's boot registration; CRUD, publish and revisions proven against the shared dev database.

⬜ Marketing surfaces

Editorial content streams and marketing surfaces.

Evidence

Streams are now a registered service, not just a mechanism: @specfocus/visualize's Content API registers content › streams and serves draft/publish documents with revision history from the content database, mounted in centralize at /content, with upload (R2 presign) and pictograph routes riding the same feature. Caveats stay real: tenancy is a tenant_id column in a single database (schema isolation is a later wave), uploads and pictographs are routes of streams rather than separately registered features, and this site's own pages are still file-based streams, not yet served from the store. Storefront content remains placeholder until the rendered pages are reverse-engineered into streams.