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

# Finance & RevOps Architecture: Domain Projection Contract

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

Finance and RevOps 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 financial operations and revenue management.

Domain contract:

```yaml theme={null}
domain: finance-revops
purpose: financial operations, revenue management, forecasting, and reconciliation
entities:
  - Contract
  - Invoice
  - Subscription
  - Revenue
  - Forecast
  - ARR/MRR
  - Customer
  - Payment
views:
  - Revenue Dashboard
  - MRR/ARR Trends
  - Renewal Forecast
  - AR Aging
  - Reconciliation Queue
  - Contract Portfolio
  - Customer Health
  - Forecast Variance
agents:
  - Twin
  - Discovery Agent
  - Triage Agent
  - Schema Agent
  - Revenue Agent
  - Reconciliation Agent
  - Renewal Agent
  - Forecast Agent
  - Collections Agent
capabilities_prefix: finrev
workflows:
  - Monthly Close
  - Renewal Booking
  - Reconciliation
  - Forecast Update
  - Revenue Recognition
integrations:
  - stripe
  - quickbooks
  - chargebee
  - netsuite
  - salesforce
  - hubspot
events:
  - invoice.issued
  - payment.received
  - contract.signed
  - subscription.changed
  - revenue.recognized
  - forecast.updated
  - renewal.at_risk
  - reconciliation.matched
```

Finance and RevOps 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/finance-revops/index)
* [Domain](/internal-docs/domains/finance-revops/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.