> ## 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.

# Marketing Architecture: Domain Projection and Contracts

> How the Marketing domain is architected as a Spine projection, including its domain contract and references to context, agent, and integration architectures.

The Marketing domain is not a separate application. It is a projection of Spine Fabric, assembled on demand from unified entities, events, and evidence. Its architecture follows the Spine domain projection model: a contract defines the schema, views, agents, capabilities, and workflows; Spine assembles the runtime state from source connectors.

## Domain Contract

```yaml theme={null}
domain: marketing
purpose: campaign management and lead generation
personas:
  - marketing_manager
  - demand_gen
  - content_marketer
  - marketing_ops
entities:
  - Campaign
  - Audience
  - Content
  - Lead
  - Attribution
  - Channel
  - Program
  - Event
views:
  - Campaign Performance
  - Attribution Funnel
  - Content Pipeline
  - Lead Flow
  - Program Calendar
agents:
  - Twin
  - Campaign Agent
  - Content Agent
  - Attribution Agent
  - Event Agent
  - Lead Nurture Agent
capabilities:
  - campaign.performance.read
  - campaign.ad_spend.adjust
  - content.asset.publish
  - workflow.campaign_launch
  - workflow.event_follow_up
integrations:
  - hubspot
  - marketo
  - salesforce
  - google_analytics
  - linkedin_ads
  - segment
  - notion
events:
  - campaign.created
  - content.published
  - lead.captured
  - lead.scored
  - campaign.performance_updated
  - event.completed
```

## Projection Architecture

Spine Fabric ingests from connected sources, normalizes to the domain contract, and projects views scoped to the requesting user. The projection layer is stateless. It queries the unified graph at request time, so views are always current.

## Context, Agent, and Capability Architectures

* **Context Architecture:** Defines how campaign graphs are assembled from entities, events, and evidence.
* **Agent Architecture:** Defines how Twin and domain agents observe, reason, delegate, and act.
* **Capability Architecture:** Defines how governed actions are authorized, executed, and receipted.
* **Workflow Architecture:** Defines how multi-step processes orchestrate capabilities across users and agents.
* **Integration Architecture:** Defines how connectors map source-system schemas to Spine entities.
* **Event Architecture:** Defines how domain events are emitted, routed, and consumed.

## Related

* [Marketing Overview](/internal-docs/domains/marketing/index)
* [Spine Fabric](/platform/spine-fabric)
* [Spine Agent Network](/agents/spine-agent-network)
* [Platform Capabilities](/platform/capabilities)


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