> ## Documentation Index
> Fetch the complete documentation index at: https://docs.integratewise.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Domain Workbenches: Overview

> The domain workbenches document how each business domain is worked in SpineWorkspace: humans, Twin, agents, Spine context, and execution.

Domain workbenches document how each business domain is worked inside SpineWorkspace. They are not a documentation abstraction; they mirror the product architecture directly. Every domain page walks through the same canonical structure so teams can compare, reuse, and hand off cleanly.

## The Canonical Structure

Every domain has 18 pages: an index and 17 canonical sections covering the four flows.

<CardGroup cols={2}>
  <Card title="Human Workbench" icon="user">
    Views, work, context, and actions the person sees.
  </Card>

  <Card title="AI Workbench" icon="robot">
    Twin, agents, skills, capabilities, workflows.
  </Card>

  <Card title="System Flow" icon="diagram-project">
    How Spine ingests, unifies, and projects the domain.
  </Card>

  <Card title="Execution Flow" icon="bolt">
    How work executes across source systems with receipts.
  </Card>
</CardGroup>

## Available Domains

| Domain                                                                              | Purpose                                          |
| ----------------------------------------------------------------------------------- | ------------------------------------------------ |
| [Account Success](/internal-docs/domains/account-success/index)                     | Customer lifecycle, health, renewal, expansion   |
| [Technical Account Success](/internal-docs/domains/technical-account-success/index) | Technical customer management and implementation |
| [Business Operations](/internal-docs/domains/business-ops/index)                    | Cross-functional operations and process          |
| [Finance & RevOps](/internal-docs/domains/finance-revops/index)                     | Financial operations and revenue                 |
| [Sales](/internal-docs/domains/sales/index)                                         | Pipeline and customer acquisition                |
| [Marketing](/internal-docs/domains/marketing/index)                                 | Campaigns and lead generation                    |
| [Content](/internal-docs/domains/content/index)                                     | Content creation and knowledge                   |
| [Service](/internal-docs/domains/service/index)                                     | Customer service and support delivery            |
| [Product Engineering](/internal-docs/domains/product-engineering/index)             | Product development and engineering              |
| [Personal](/internal-docs/domains/personal/index)                                   | Personal productivity and work management        |
| [Human Resources](/internal-docs/domains/human-resources/index)                     | People operations and talent                     |
| [Legal](/internal-docs/domains/legal/index)                                         | Legal counsel and compliance                     |
| [Support](/internal-docs/domains/support/index)                                     | Technical support and issue resolution           |
| [Founder Ops](/internal-docs/domains/founder-ops/index)                             | Founder and executive operations                 |
| [Operations](/internal-docs/domains/operations/index)                               | General operations and administration            |

## Key Principle

Domain documentation does not document a collection of screens. It documents how a business domain is worked by humans, assisted by Twin and its workers, contextualized by Spine, processed by the system, and executed across connected source systems.