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

# Business Operations Architecture: Domain Projection Contract

> How Business Operations is architected as a Spine Fabric projection, including the domain contract and references to shared platform architecture.

Business Operations is not an application. It is a domain projection of the Spine Fabric, rendered through a domain contract that defines entities, views, agents, capabilities, and events specific to operational work.

Domain contract:

```yaml theme={null}
domain: business-ops
purpose: cross-functional operations management and process optimization
entities:
  - Process
  - Workflow
  - Approval
  - Vendor
  - Contract
  - Policy
  - OKR
  - Initiative
views:
  - Active Initiatives
  - Pending Approvals
  - Vendor Portfolio
  - Process Health
  - Policy Registry
  - OKR Dashboard
  - Spend Overview
  - Exception Log
agents:
  - Twin
  - Discovery Agent
  - Triage Agent
  - Schema Agent
  - Approval Agent
  - Vendor Agent
  - Policy Agent
  - OKR Agent
  - Process Agent
capabilities_prefix: bizops
workflows:
  - Approval
  - Vendor Onboarding
  - Policy Review
  - OKR Cycle
  - Process Improvement
integrations:
  - google_workspace
  - asana
  - notion
  - linear
  - hris
  - erp
events:
  - workflow.started
  - approval.requested
  - approval.resolved
  - vendor.onboarded
  - policy.attested
  - okr.progress.updated
  - contract.renewed
  - process.improvement.proposed
```

Business Operations inherits shared platform architecture:

* Domain Projection: how the Fabric renders domain-specific views from unified context.
* Context Architecture: how entity resolution and dossier assembly work across connectors.
* Agent Architecture: how Twin and agents coordinate through events and handoffs.
* Capability Architecture: how authorization, scope, and receipts govern every action.
* Workflow Architecture: how workflow definitions, instances, and state are modeled.
* Integration Architecture: how connectors ingest, normalize, and write back to source systems.
* Event Architecture: how events flow through Spine for real-time updates and audit.

**Related**

* [Overview](/internal-docs/domains/business-ops/index)
* [Domain](/internal-docs/domains/business-ops/domain)
* [Spine Fabric](/platform/spine-fabric)
* [Platform Capabilities](/platform/capabilities)
* [Platform Connectors](/platform/connectors)


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