{"slug":"ai/twin-execution","title":"08 · Twin Execution","section":"ai","sectionLabel":"AI","status":"unclassified","type":"document","path":"ai/twin-execution.mdx","bytes":3864,"description":"The Twin is the human-facing AI coworker, not a separate Workbench. Identity, relationship to user, personal context, AI continuity, business context, current work, capabilities, authority, governed execution, memory, handoff.","updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n## Twin Is the Human-Facing AI Coworker\n\n\n**Twin ≠ AI Workbench.** The AI Workbench is the operating environment. Twin is the coworker who operates within it.\n\n\n```text\nBUSINESS CONTEXT SPINE\n        │\n        ▼\n  AI WORKBENCH (projection over BC)\n        │\n        ├── Twin  ← you are here\n        │     identity: twin:{userId}\n        │     bound to human, tenant, authority\n        ├── Agent runtime\n        ├── Model routing / ADK\n        └── Capability access (governed)\n        │\n        ▼\n  AI CONTINUITY MEMORY (serves BC)\n        │\n        ▼\n   Shared Work / Evidence / Verify → Spine\n```\n\n## Twin Identity & Relationship to User\n\n| Property | Value |\n|---|---|\n| **Identity** | `twin:{userId}` — one per human, tenant-scoped |\n| **Relationship** | Knows personal context, current Work, and what the user is authorized to see |\n| **Projection** | Hydrates the same Active Context Bundle as the Human Workbench for the same Work |\n| **Continuity** | AI Continuity Memory — Twin's working continuity that serves Business Context |\n| **Authority** | Same authorization surface as the user, but never owner of decisions or approvals |\n\n## What Twin Does in a Work Context\n\n\n  \n    Receives the Active Context Bundle: Business Context slice + Work + evidence + authority + AI Continuity relevant to this Work and user.\n  \n  \n    Assembles precise context, reasons over it, and prepares a plan or draft — scoped to the Work objective andBusiness Context.\n  \n  \n    Proposes a plan: capability, inputs, sequencing, and what will need approval. Surfaces business context, not raw tool payloads.\n  \n  \n    Submits the plan to governance. If authorized, hands subtasks to Spine Agents via Shared Work or executes via Hermes. Never bypasses approval.\n  \n  \n    Observes outcome, captures evidence, assists verification/reconciliation, and leaves continuity so the human or next agent continues without re-briefing.\n  \n\n\n## Capabilities & Authority\n\n* Twin selects **provider-neutral capabilities** via the [Capability Fabric](/platform/capability-fabric-view), not hard-coded tool calls.\n* Twin never executes external mutations without a **governance verdict**.\n* Every Twin action is **traced and evidence-linked** to the Work and the Business Context it operated on.\n\n## Memory & Handoff\n\n* Twin's working notes live in **AI Continuity Memory** (serving Business Context, not replacing it).\n* On handoff, the next participant (human or agent) hydrates from **Shared Work + Business Context**, not from a pasted Twin transcript.\n\n```text\nUser thought ≠ AI inference ≠ Organizational truth\n```\n\nPromotion of a Twin inference to organizational truth requires the same path as any AI working item: Triage / Governance / governed write → verify → reconcile → Spine.\n\n## Where to Go Next\n\n<CardGroup cols={2}>\n  \n    The operating environment Twin lives in.\n  \n  \n    When Twin hands a subtask to a governed organizational actor.\n  \n  \n    Three domains and G-10: AI Continuity scope vs persistent substrate.\n  \n</CardGroup>\n"}