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

# Twin: Your Personal AI Operator in SpineWorkspace

> Twin is your personal AI operator inside SpineWorkspace. It works on the same shared, governed context you do, and acts only with your authority.

Twin is your personal AI operator inside SpineWorkspace. It sees the same shared, governed business context you see, works on the same journey you are on, and acts only under your authority. Twin is the AI half of the human plus AI operating model that SpineWorkspace is built for.

## What Twin Is

Twin is not a chatbot bolted onto a tool. Twin is an operator that lives in the workspace, is projected into your domain, and inherits your context, your identity, and your governance boundaries. It reasons over the same picture of the business that you have, and it proposes and executes work through governed capabilities.

<CardGroup cols={2}>
  <Card title="Contextual" icon="brain">
    Twin operates over Spine Fabric, so every task begins with the current, unified picture of the business.
  </Card>

  <Card title="Personal" icon="user">
    Twin inherits your role, portfolio, and authority. Its view is your view, projected for the work in front of you.
  </Card>

  <Card title="Governed" icon="shield-check">
    Every write goes through governed capabilities. Twin acts under your authority, never in place of it.
  </Card>

  <Card title="Continuous" icon="infinity">
    Twin's working memory operates inside business continuity, so nothing is lost between sessions, handoffs, or agents.
  </Card>
</CardGroup>

## What Twin Does

<Steps>
  <Step title="Observes">
    Twin watches signals across the connected systems in your domain: new events, changes, tickets, meetings, deadlines, and alerts.
  </Step>

  <Step title="Orients">
    Twin assembles context around the work in front of you, pulling the entities, events, evidence, and history relevant to the moment.
  </Step>

  <Step title="Reasons">
    Twin decides what matters, what is urgent, what should wait, and what needs a human. It drafts, summarizes, and prepares proposals.
  </Step>

  <Step title="Delegates">
    For work outside its expertise, Twin routes to core agents, domain agents, or specific capabilities across the Spine Agent Network.
  </Step>

  <Step title="Proposes">
    Twin surfaces recommended actions with the context and evidence attached. You approve, edit, or reject.
  </Step>

  <Step title="Acts">
    On approval, Twin executes governed capabilities that write back to source systems and produce receipts.
  </Step>
</Steps>

## Why Twin Is Different

Most copilots live inside one tool and see only that tool. Twin lives in SpineWorkspace and sees the whole business through Spine Fabric. That difference changes what Twin can do:

* Reason across CRM, support, docs, product usage, and finance at the same time.
* Carry a decision from one system into the next with continuity intact.
* Coordinate with other agents through the Spine Agent Network.
* Preserve receipts and evidence so every action is traceable and reviewable.

<Note>
  Twin's memory is AI memory: the working state Twin needs to do its job. It operates inside business continuity, not in place of it. The durable, governed memory of the business lives in Spine Fabric.
</Note>

## Human Authority, Always

Twin never bypasses you. You set intent, judgement, approvals, and direction. Twin does the heavy, monotonous, and tedious lifting so you can spend attention where it matters. On any action that touches a system of record, an approval loop is available and receipts are produced.

## Related

* [Human + AI Model](/product/human-ai-operating-model)
* [Shared Context](/product/shared-context-principle)
* [SpineWorkspace](/product/spine-workspace)
* [Spine Agent Network](/agents/spine-agent-network)
* [Governed Actions](/how-it-works/governed-actions)