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

# Service Domain Architecture: Projection and Contract Design

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

The Service 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: service
projections:
  - name: case_queue
    sources: [zendesk, salesforce, freshdesk, intercom]
    entities: [case, customer, agent]
    frequency: realtime
  - name: sla_dashboard
    sources: [zendesk, salesforce, freshdesk]
    entities: [case, sla, customer]
    frequency: realtime
  - name: escalations
    sources: [zendesk, salesforce, freshdesk, intercom]
    entities: [case, escalation, agent]
    frequency: realtime
  - name: customer_history
    sources: [zendesk, salesforce, freshdesk, intercom, twilio]
    entities: [customer, case, interaction, feedback]
    frequency: realtime
  - name: agent_performance
    sources: [zendesk, salesforce, freshdesk]
    entities: [agent, case, resolution, feedback]
    frequency: hourly
  - name: feedback_summary
    sources: [zendesk, freshdesk, intercom]
    entities: [feedback, case, customer]
    frequency: hourly
  - name: interaction_log
    sources: [zendesk, intercom, twilio]
    entities: [interaction, case, customer]
    frequency: realtime
agents:
  - twin
  - discovery_agent
  - triage_agent
  - schema_agent
  - resolution_agent
  - escalation_agent
  - sla_agent
  - feedback_agent
capabilities:
  - service.case.*
  - service.customer.*
  - service.sla.*
  - service.escalation.*
  - service.interaction.*
  - service.feedback.*
  - service.workflow.*
  - service.approval.*
  - service.handoff.*
events:
  - case.opened
  - assigned
  - interacted
  - escalated
  - resolved
  - sla.breached
  - feedback.received
```

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

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


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