> ## Documentation Index
> Fetch the complete documentation index at: https://docs.spineworkspace.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Content Domain Architecture: Projection and Contract Design

> Understand how the Content domain is architected as a Spine Fabric projection, including its domain contract and component relationships.

The Content domain is not a separate application. It is a projection of the Spine Fabric, assembled on demand from unified entities, events, and evidence. Its architecture follows the standard domain projection pattern used across SpineWorkspace.

### Domain Contract

```yaml theme={null}
domain: content
projections:
  - name: editorial_calendar
    sources: [notion, google_drive, confluence]
    entities: [article, campaign, author]
    frequency: realtime
  - name: content_pipeline
    sources: [notion, github, contentful]
    entities: [article, version, author]
    frequency: realtime
  - name: publication_queue
    sources: [wordpress, contentful, hubspot]
    entities: [article, publication]
    frequency: realtime
  - name: knowledge_base
    sources: [confluence, notion, wordpress]
    entities: [article, topic, category]
    frequency: hourly
  - name: asset_library
    sources: [google_drive, contentful]
    entities: [asset, article, campaign]
    frequency: realtime
agents:
  - twin
  - discovery_agent
  - triage_agent
  - schema_agent
  - editorial_agent
  - publish_agent
  - asset_agent
  - translation_agent
capabilities:
  - content.article.*
  - content.asset.*
  - content.campaign.*
  - content.publication.*
  - content.review.*
  - content.workflow.*
  - content.approval.*
  - content.handoff.*
events:
  - article.created
  - draft.updated
  - review.requested
  - review.approved
  - published
  - versioned
  - asset.uploaded
```

### Component Relationships

* **Domain Projection** — maps source records to unified views using the contract above.
* **Context Assembly** — builds practitioner context by linking entities, events, and evidence on demand.
* **Agent Runtime** — executes Twin and domain agents with access to context and skills.
* **Capability Layer** — enforces authorization, scope, and receipts for every action.
* **Workflow Engine** — orchestrates multi-step processes with handoffs and approvals.
* **Integration Layer** — manages connectors and MCP interfaces to source systems.
* **Event Bus** — propagates state changes so views and agents stay synchronized.

### Related

* [Content Spine Fabric](/internal-docs/domains/content/spine-fabric)
* [Content System Flow](/internal-docs/domains/content/system-flow)
* [Content Execution Flow](/internal-docs/domains/content/execution-flow)
* [Platform Spine Fabric](/platform/spine-fabric)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.