{"slug":"business/25-twin-story","title":"25 — Twin Story","section":"business","sectionLabel":"Business","status":"unclassified","type":"document","path":"business/25-twin-story.mdx","bytes":5175,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\nStatus: CANONICAL · Commercial OS\nOwner: Product Marketing\nLast verified: 2026-07-21\n\n---\n\n## Purpose\n\nHow to tell the Twin — the concept most at risk of being misheard as \"chatbot.\" This story exists to make the difference unmissable.\n\n**Definition (verbatim):** _A person's governed AI counterpart that works alongside them on the same workbench — it prepares, suggests, and proposes; it never owns truth and never acts without approval._\n\n---\n\n## 1. The Story\n\nEveryone has met the other kind of AI. It lives in a tab. It knows nothing about your morning until you paste your morning into it. It answers with confidence, sometimes about things that aren't true. It forgets you by tomorrow — or worse, remembers something it invented about you. You learned its real place: emails, summaries, nothing that matters. The quiet demotion.\n\nThe Twin is built from the opposite premises. It is **yours** — one Twin per person, scoped by your role and authority, at your bench. It **already knows the context**, because it shares your workbench and reads the same Spine of truth you do — it never asks you to re-explain your own work. It **prepares the hard parts**: the meeting brief before you open it, the analysis behind the risk signal, the draft grounded in what was actually said. It **shows its evidence** — every claim links to sources; and when it has nothing grounded to offer, **it is silent**. No filler, no vibes, no invented renewal dates.\n\nAnd the line it cannot cross, by architecture: **the Twin proposes; you approve.** It cannot write to organizational memory — TruthLayer requires your approval. It cannot execute a consequential action — governance requires your approval. It is a colleague with excellent preparation and no authority — which is exactly why you can finally give it consequential work.\n\n> The experience promise, verbatim: _\"My work already knows its context. AI prepared the hard parts. I decide.\"_\n\n## 2. What the Twin Does (grammar, not feature list)\n\n`NOTICE` what changed and matters · `EXPLAIN` this work from its context · `RELATE` this to what the org knows · `PREPARE` the brief/analysis/draft · `SUGGEST` the next step · `PROPOSE` the reviewable action.\n\nAnd what it never does (doctrine): own truth or memory · own identity, policy, or authorization · execute unapproved · occupy a permanent chat destination that competes with the work.\n\n## 3. The Hard Distinctions (say these before the prospect asks)\n\n| They think                     | The correction                                                                                                                                                                                                    |\n| ------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| \"So it's a chatbot on my data\" | A chatbot is a _destination_ — you go to it and narrate. The Twin is at the bench: its help lands inside the work, grounded, with evidence.                                                                       |\n| \"Like a copilot?\"              | Copilots are sidecars to one app and see that app. Your Twin works over your organization's assembled truth — every connected system, one context. \"Copilots visit your apps. IntegrateWise is where work lives.\" |\n| \"An autonomous agent then\"     | The opposite bet. Agents seek autonomy; the Twin's contract is preparation + proposal, with your approval gating anything real. That contract is _why_ it gets real work.                                         |\n| \"Will it replace my team?\"     | It's one-per-person, not one-instead-of-person. The accountable human is the design center — the Twin amplifies them.                                                                                             |\n\n## 4. Trust Mechanics (why belief is not required)\n\nEvidence chains on interventions · TruthLayer approval on memory · action approval + audit trail · confidence honesty (silence over speculation) · model-agnostic (swap the AI; the Twin's knowledge stays, because knowledge lives in _your_ Spine).\n\n**Trust line, verbatim:** \"Every AI remembers. Only IntegrateWise remembers the truth.\"\n\n## 5. Language Rules\n\n- Always \"your Twin\" (possessive, singular, capital T). Never \"the AI,\" \"the bot,\" \"our assistant,\" \"agents.\"\n- Verbs of preparation and proposal, never verbs of autonomous completion (\"your Twin drafted\" ✓ · \"your Twin handled it\" ✗).\n- The human decides in every sentence where something consequential happens.\n\n**KPIs:** Approved Twin Actions per seat/week (north star); intervention acceptance rate; \"chatbot\" misreadings in discovery (should trend to zero as messaging lands) ([73](../13-operations/73-marketing-metrics.md)).\n\n---\n\n**Related:** [24 Workbench Story](24-shared-workbench-story.md) · [27 Governance Story](27-governance-story.md) · [22 Spine Story](22-adaptive-spine-story.md) · [12 Messaging](../03-positioning-messaging/12-messaging-framework.md)\n"}