{"slug":"strategy/business-strategy/INTEGRATED_VISION","title":"IntegrateWise: Integrated Vision","section":"strategy","sectionLabel":"Strategy","status":"unclassified","type":"document","path":"strategy/business-strategy/INTEGRATED_VISION.mdx","bytes":15789,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n> **Tier C — Historical.** This document is a point-in-time snapshot preserved for reference. For current architecture, see [CANONICAL_PLATFORM_ARCHITECTURE.md](../architecture/CANONICAL_PLATFORM_ARCHITECTURE.md).\n\n**Recovery + Activation = Platform-First Human Experience**\n\n---\n\n## The Three Breakthroughs\n\n### 1. Recovery Vision: Human Workbench is Primary\n> \"Stop Being Human APIs\" — January 2025 insight\n\nThe workbench is not a feature. It is THE product.\n- Dashboard, Contacts, Companies, Opportunities\n- Tasks, Calendar, Notes, Meetings, Communications\n- Knowledge, Goals, Values, Reports, Settings\n- 15+ surfaces, all configurable\n\nAI Twin has its own home (separate, not interrupting).\nContinuity Engine owns memory (invisible backbone).\n\n### 2. Platform Activation: Frozen Contracts + SDK\n> \"Every frontend is a Projection\" — Architecture insight\n\nEight frozen contracts make IntegrateWise replaceable:\n1. PlatformRequest/Response (envelopes)\n2. Capability (atomic work unit)\n3. Entity (what Capability operates on)\n4. Memory (knowledge with boundaries)\n5. Proposal/Approval (decision lifecycle)\n6. Projection (how Capability renders per lens)\n7. + two more (ToolAction, ProviderAction)\n\n@integratewise/sdk makes any frontend functional:\n```typescript\nconst iw = new IntegrateWise({ tenant, identity, runtime })\nconst health = await iw.accounts.health(accountId)\n```\n\n### 3. The Synthesis: Adaptive Platform\nWhen you combine both:\n- **Recovery:** Workbench is human-centric, eight lenses (Sales, CS, Finance, Ops, HR, Exec, Personal)\n- **Activation:** Those eight lenses become Projections via iw.workbench.lens()\n- **Result:** Any frontend using @integratewise/sdk becomes an IntegrateWise workbench\n\n---\n\n## Architecture Diagram\n\n```\n                            HUMAN WORKBENCH (Recovery Vision)\n                    (Dashboard + 15 Surfaces + Configurability)\n\n        Sales    CS    Finance    Ops    HR    Exec    Personal\n         │       │        │       │     │      │         │\n         └─────────────────┴───────┴─────┴──────┴─────────┘\n                            │\n                            ▼\n            ┌───────────────────────────────┐\n            │  Projection Layer             │\n            │  (iw.workbench.lens(...))     │\n            └───────────────────────────────┘\n                            │\n                            ▼\n            ┌───────────────────────────────┐\n            │  @integratewise/sdk           │\n            │  (Frozen Capability APIs)     │\n            └───────────────────────────────┘\n                            │\n  ┌─────────────────────────┼─────────────────────────┐\n  ▼                         ▼                         ▼\nLovable                   v0                      Replit\n(via SDK)              (via SDK)                (via SDK)\n  │                         │                         │\n  └─────────────────────────┼─────────────────────────┘\n                            │\n                            ▼\n    ════════════════════════════════════════════════════════════\n          IntegrateWise Platform (Frozen Contracts)\n    ════════════════════════════════════════════════════════════\n                            │\n        ┌───────────────────┼───────────────────┐\n        ▼                   ▼                   ▼\n  Capability Engine    Memory Spine         Governance\n  • Renewal Risk       • Entity360          • Approvals\n  • Account Health     • Scopes             • Audit\n  • AR Exposure        • TTLs               • Policies\n  • 50+ more           • Redaction          • Rate Limits\n        │                   │                   │\n        └───────────────────┼───────────────────┘\n                            │\n                            ▼\n            ┌───────────────────────────────┐\n            │  Continuity Bridge (Front Door)\n            │  • Connection Management      │\n            │  • Tenant Isolation           │\n            │  • OAuth Once, Reuse Always   │\n            └───────────────────────────────┘\n                            │\n                            ▼\n    Connected Applications (100+)\n    Gmail · Slack · GitHub · Figma · Notion · Salesforce · ...\n```\n\n---\n\n## How It Works: Three Scenarios\n\n### Scenario 1: Sales User at Beginning of Day\n\n```typescript\n// Behind the scenes: iw.workbench.lens(\"Sales\")\n\n\nconst iw = new IntegrateWise({\n  tenant: \"acme-corp\",\n  identity: \"sarah@acme.com\",\n  runtime: \"browser\"  // v0 frontend\n})\n\n// 1. Get accounts with health scores\nconst accounts = await iw.accounts.list()\nconst health = await Promise.all(\n  accounts.map(acc => iw.accounts.health(acc.id))\n)\n\n// 2. See what needs renewal attention\nconst renewal = await iw.capability(\"renewal-risk\", {\n  accounts: accounts.slice(0, 10)\n})\n\n// 3. Review proposals waiting for approval\nconst proposals = await iw.proposals.list({\n  status: \"pending\",\n  lens: \"Sales\"\n})\n\n// Result: Sales Dashboard populated via pure SDK calls\n// Same result from Lovable, Replit, Electron, Next.js\n// because all call same SDK against same Spine\n```\n\n### Scenario 2: CS Manager via Replit Frontend\n\n```typescript\n// Behind the scenes: iw.workbench.lens(\"CustomerSuccess\")\n\nconst iw = new IntegrateWise({\n  tenant: \"acme-corp\",\n  identity: \"marcus@acme.com\",\n  runtime: \"browser\"  // Replit frontend\n})\n\n// 1. Get all accounts flagged as at-risk\nconst atRisk = await iw.memory.search({\n  query: \"at-risk status\",\n  scope: [\"org\"],  // Organization-scoped memory\n  topK: 20\n})\n\n// 2. Create expansion opportunity proposals\nconst proposals = await Promise.all(\n  atRisk.map(risk => \n    iw.proposals.create(\n      \"expansion-opportunity\",\n      {\n        account: risk.id,\n        opportunity: \"upsell to premium\",\n        expectedARR: 50000\n      },\n      \"Customer engagement trending up 3 months\"\n    )\n  )\n)\n\n// 3. Get QBR briefs for this week\nconst qbrs = await iw.capability(\"qbr-brief\", {\n  period: \"this-week\",\n  lens: \"CustomerSuccess\"\n})\n\n// Result: CS Dashboard identical regardless of frontend\n```\n\n### Scenario 3: Executive Getting Daily Brief\n\n```typescript\n// Behind the scenes: iw.workbench.lens(\"Executive\")\n\nconst iw = new IntegrateWise({\n  tenant: \"acme-corp\",\n  identity: \"ceo@acme.com\",\n  runtime: \"server\"  // Next.js server component\n})\n\n// 1. Get strategy summary\nconst strategy = await iw.strategy.summary(\"this-month\")\n\n// 2. Get KPI dashboard\nconst kpis = await iw.analytics.run({\n  metric: \"arr_by_cohort\",\n  groupBy: [\"segment\", \"region\"],\n  period: { start: thisMonthStart, end: today }\n})\n\n// 3. Get risk register\nconst risks = await iw.memory.search({\n  query: \"strategic risk\",\n  scope: [\"org\"],  // org-level memory only\n  topK: 10\n})\n\n// 4. Get pending executive approvals\nconst pending = await iw.proposals.list({\n  approvals: { actor: { id: \"ceo@acme.com\", type: \"human\" } },\n  status: \"pending\"\n})\n\n// Result: Executive dashboard with real KPIs\n// Same data whether accessed from Vercel UI, Next.js app, or Electron\n```\n\n---\n\n## Key Principles (Integration)\n\n### 1. One Platform, Many Surfaces\nThe workbench isn't built once—it's projected eight times:\n- **Sales:** Focus on pipeline, renewal, expansion\n- **CS:** Focus on health, risk, expansion\n- **Finance:** Focus on AR, AP, forecast\n- **Ops:** Focus on workflow, SLA, capacity\n- **HR:** Focus on people, retention, succession\n- **Exec:** Focus on strategy, KPIs, risk\n- **Personal:** Focus on goals, reflection, life\n- **Emerging:** (Easy to add new lenses)\n\nEach lens is a **Projection** — a different view of the same Adaptive Spine.\n\n### 2. Business Logic Lives in Capabilities, Not UIs\n- Renewal Risk Capability exists once, everywhere\n- CS user sees it in CS lens, Sales user in Sales lens\n- Twin can call it for daily routines\n- API can call it for integrations\n\nIf logic varies by UI, **that's a bug in the Capability contract**, not a feature.\n\n### 3. Memory Has Boundaries, Not Walls\n```\nOrganization Memory   (shared across team)\n  ├─ Strategic risk register\n  ├─ Customer segments\n  └─ Competitive intelligence\n\nWork Memory           (shared across projects)\n  ├─ Sprint goals\n  ├─ Technical decisions\n  └─ Meeting notes\n\nPersonal Memory       (individual only)\n  ├─ Goals + reflections\n  ├─ Career development\n  └─ 1:1 notes with manager\n\nAudit Memory          (system only)\n  ├─ All approvals\n  ├─ All large changes\n  └─ Compliance trail\n```\n\nHuman ↔ Twin memories are **separate but shared** (no human memory erased, Twin gets its own).\n\n### 4. Twin is Operational Participant, Not Product\nTwin:\n- Observes patterns daily\n- Maintains own memory + learnings\n- Has daily routines (not random)\n- Collaborates via overlay (not interrupting)\n- Answers questions when asked\n- **Never** replaces workbench\n\nTwin's home is **separate** from human workbench.\nWhen Twin adds value (daily insights, draft proposals), it surfaces in workbench via Capabilities.\n\n### 5. The SDK is the Covenant\n```typescript\n@integratewise/sdk is the contract.\n\niw.accounts.list()               → Same everywhere\niw.capability(\"renewal-risk\"...)  → Same everywhere\niw.proposals.create(...)          → Same everywhere\niw.workbench.lens(\"Sales\")        → Same everywhere\n\nNo frontend gets special behavior.\nNo endpoint exists outside the SDK.\nNo business logic hides in a tool.\n```\n\n---\n\n## Execution: How They Converge\n\n### Phase 1: Recovery (Weeks 1-2)\n- Clean v0 experimental files\n- Deploy restored Human Workbench\n- Customer Zero begins real work\n- Spine starts ingesting patterns\n\n**Goal:** Workbench is primary, not overlay.\n\n### Phase 2: Schema Evolution (Week 3)\n- Spine Schema v1.0 emerges from real usage\n- Entity types, relationships, boundaries defined\n- 150+ entities, 500+ relationships indexed\n- Memory scopes validated\n\n**Goal:** Platform has canonical data model.\n\n### Phase 3: Platform Activation (Weeks 4-6)\n- Phase A backend services reach v1.0 (Capability Registry, Entity360, Governance, etc.)\n- Platform contracts frozen\n- @integratewise/sdk published and tested\n- Frontend swap validation passes\n\n**Goal:** Business logic provably in Capabilities, not UIs.\n\n### Phase 4: Full Integration (Weeks 7-8)\n- All eight Workbench lenses operational\n- All Projections calling iw.workbench.lens()\n- Each lens independently configurable\n- Twin AI Workbench integrated\n\n**Goal:** Human-centric platform proven + platform-first proven = complete.\n\n---\n\n## Success Looks Like\n\n**From User Perspective:**\n```\nMonday morning, Sales user opens v0 workbench\n  → Dashboard shows all accounts + health + renewal risk\n  → Can create renewal proposals with one click\n  → Proposals queue for CS review (separate step)\n  → All configurable: show/hide columns, reorder, pin favorites\n\nTuesday, CS manager opens Replit workbench (same company)\n  → Same data, different lens (health-focused, not pipeline)\n  → Can see why renewals are at risk (Twin's observations)\n  → Can create expansion proposals (to Sales for approval)\n  → Identical data, different interpretation\n\nThursday, CEO opens Lovable dashboard\n  → Executive lens shows KPIs, risks, strategy summary\n  → All from same Spine, same Capabilities\n  → Read-only for most, can approve big decisions\n  → Byte-identical to what CEO would see in Next.js app\n```\n\n**From Technical Perspective:**\n```\nAcceptance Test Passes:\n  ✓ Build \"account-health\" screen in v0\n  ✓ Build \"account-health\" screen in Replit\n  ✓ Build \"account-health\" screen in Lovable\n  ✓ All call iw.capability(\"account-health\", args)\n  ✓ All return identical results\n  ✓ UI differences (colors, layout) don't matter\n  ✓ Business logic (health calculation) is identical\n\nPlatform Proven:\n  ✓ Every method in SDK is a Capability\n  ✓ Every Capability has governance\n  ✓ Every Capability has a version\n  ✓ Business logic doesn't leak into frontends\n  ✓ Adding a new frontend = day of work (SDK integration)\n  ✓ Adding a new Capability = internal work (backend only)\n```\n\n---\n\n## What's Different After Integration\n\n### Before\n- \"Which tool should we rebuild this in?\" (Lovable? v0? Replit?)\n- Business logic scattered across multiple frontends\n- Each new tool = months of rebuilding\n- Continuity depends on manual note-taking\n\n### After\n- \"What Capability do we need?\" (renewal-risk? account-health? forecast?)\n- Business logic lives in Capability, not UI\n- Each new tool = days (just implement Projections)\n- Continuity is automatic via Spine\n\n### Before\n- Workbench is one of many \"agents\"\n- AI is the primary product, humans are users\n- Context is ephemeral (lost between sessions)\n\n### After\n- Workbench is the primary product\n- AI is invisible infrastructure (powerful but not prominent)\n- Context is persistent (Spine remembers everything)\n\n---\n\n## The Real Product\n\nNot: \"MultiModel AI Orchestration\"\nNot: \"Capability Engine\"\nNot: \"Adaptive Spine\"\n\n**Yes:** \"Nothing is lost in context.\"\n\nWhen Sarah (Sales) works in v0, then switches to Replit, then hands off to Marcus (CS):\n- Marcus sees everything Sarah saw\n- Marcus sees what Twin observed\n- Marcus knows Sarah's proposals are waiting\n- Marcus can pick up exactly where Sarah left off\n- No context switching cost\n- No information re-entering\n- No missed details\n\nThat's the product.\nThat's what people buy.\nThat's what makes the moat.\n\n---\n\n## Roadmap Summary\n\n| Phase | What | Duration | Milestone |\n|-------|------|----------|-----------|\n| **0** | Stabilize | 2 weeks | Continuity Bridge + Vercel |\n| **1** | Recover | 2 weeks | Human Workbench Primary |\n| **2** | Evolve | 1 week | Spine Schema v1.0 |\n| **A** | Backend | 6 weeks | Services at v1.0 |\n| **B** | Contracts | 2 weeks | Frozen + Versioned |\n| **C** | SDK | 3 weeks | @integratewise/sdk Ships |\n| **D** | Validation | 2 weeks | Acceptance Test Passes |\n| **E** | Platform | 3 weeks | All Surfaces Unified |\n\n**Total: ~12 weeks to \"Platform is proven and human-centric.\"**\n\n---\n\n## What Needs to Happen Now\n\n1. **Freeze decision:** Is this architecture the target? (Yes/No/Refine)\n2. **Commit to phases:** Are you executing in this order?\n3. **Assign owners:** Who owns each service (Capability Registry, Memory, etc.)?\n4. **Define \"done\":** What proves each phase is complete?\n\nIf yes to all four: execution starts tomorrow.\n\n---\n\n*Integration: Recovery Vision + Platform Activation*\n*Product: Nothing Lost in Context*\n*Moat: Adaptive Platform Behind Frozen Contracts*\n*Timeline: 12 weeks to proof*\n\n"}