Content Domain: How Spine Fabric Assembles Context - Spine Innov Labs

Spine Fabric is the engine that turns scattered content signals into a coherent domain. For the Content domain, this means ingesting drafts, comments, tasks, and files from multiple systems and presenting them as one unified workbench.

Sources and Scopes

Source	Scope	Data Provided
Notion	Workspace pages, databases	Drafts, calendars, task lists, topics
Google Drive	Folders, docs, media	Assets, drafts, comments
Confluence	Spaces, pages	Published knowledge, versions
WordPress	Posts, pages, media	Published content, publication dates
GitHub	Repos, issues, PRs	Technical docs, review threads
Contentful	Entries, assets	Structured content, media
HubSpot	Blog posts, campaigns	Campaign metadata, publish status

Event Sequence

Ingest — Spine pulls updates on a schedule or via webhook.
Normalize — Entities like Article and Asset are mapped to a shared schema.
Enrich — Topics, categories, and relationships are inferred or linked.
Assemble — A practitioner’s current context (open items, assignments, campaigns) is built on demand.
Project — The assembled context is rendered into Editorial Calendar, Content Pipeline, and other views.

When a writer updates a Notion draft, Spine Fabric emits an event, refreshes the pipeline, and may notify Twin to propose a next step.