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

# Account Success Architecture: Domain Projection Design

> How the Account Success domain is architected as a Spine Fabric projection including the domain contract and reference to platform architectures.

Account Success is architected as a domain projection over Spine Fabric. It does not maintain separate data stores. All context is assembled on demand from the unified entity graph and governed by a domain contract.

## Domain Contract

```yaml theme={null}
domain:
  name: account-success
  purpose: customer lifecycle management, renewal, expansion, health optimization
  personas:
    - csm
    - cs_leader
  entities:
    - Account
    - Customer
    - Contact
    - Contract
    - Opportunity
    - Usage
    - Ticket
    - HealthScore
    - SuccessPlan
    - QBR
  source_systems:
    - salesforce
    - hubspot
    - gainsight
    - zendesk
    - stripe
  views:
    - AccountPortfolio
    - AtRiskAccounts
    - RenewalsPipeline
    - QBRSchedule
    - ExpansionPipeline
  workflows:
    - Renewal
    - Escalation
    - QBR
    - Onboarding
    - Expansion
  agents:
    - twin
    - renewal_agent
    - escalation_agent
    - qbr_agent
    - expansion_agent
    - success_plan_agent
  capabilities:
    prefix: account_success
    categories:
      - read
      - write
      - communication
      - workflow
```

## Projection Architecture

The Account Success projection is a read model over Spine Fabric. When a CSM queries their portfolio, Spine executes the projection logic against current unified entities. No cached copy is served unless the source systems are unreachable, and even then the cache is labeled with freshness.

## Context Assembly Architecture

Context assembly uses the entity graph, event log, and relationship index. For an account query, Spine traverses contacts, contracts, opportunities, tickets, usage events, and health scores. It applies domain scoping rules to filter by ownership, tier, and time.

## Agent Architecture

Twin orchestrates domain agents through intent messages. Agents have isolated skill implementations but share the context fabric. The Renewal Agent does not access billing data directly; it requests scoped context from Spine Fabric.

## Capability and Workflow Architecture

Capabilities are defined in the platform capability registry and bound to Account Success at runtime. Workflows are state machines with defined transitions, approval gates, and receipt generation. See the platform capability and workflow documentation for the underlying framework.

## Integration Architecture

Connectors manage protocol translation, authentication, and rate limiting for each source system. The Salesforce connector handles SOQL queries and REST API calls. The Zendesk connector manages ticket API access. See platform connector architecture for implementation patterns.

## Event Architecture

Account Success emits and consumes domain events through Spine Fabric's event bus. Events are typed, versioned, and routed to interested agents and views. Continuity persists session events for cross-session state reconstruction.

## Related

* [Account Success Index](/internal-docs/domains/account-success/index)
* [Spine Fabric](/internal-docs/domains/account-success/spine-fabric)
* [System Flow](/internal-docs/domains/account-success/system-flow)
* [Execution Flow](/internal-docs/domains/account-success/execution-flow)
* [Platform Spine Fabric](/platform/spine-fabric)


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