{"slug":"strategy/business-strategy/plan","title":"IntegrateWise Architecture Completion Plan","section":"strategy","sectionLabel":"Strategy","status":"unclassified","type":"document","path":"strategy/business-strategy/plan.mdx","bytes":4556,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n## Objective\n\nProduce the canonical, complete architecture specification for IntegrateWise Continuity Bridge v2.0 that unifies all prior work into one document covering the 6-layer architecture, OODA runtime, HITL governance, Ecosystem Fabric, and Security Model.\n\n## Background from Prior Work\n\n- **Architecture Spec v1.0.1-FINAL**: 26 services, 4 layers, adapter pattern, 0-16 stack, MCP pools, governance gates\n- **Reality Audit**: 19/26 services exist, 7 missing, Supabase entanglement, marketing bloat\n- **FINAL_E2E_SYSTEM.md**: Canonical end-to-end specification with all §14 conflicts resolved\n- **HITL Orchestrator**: 5-step human-in-the-loop with OODA annotations\n- **6-Layer Architecture**: Identity → Ingress → Capability → Continuity → Governance → Provider Fabric\n- **OODA Model**: Observe (pipelines) → Orient (agents) → Decide (hybrid) → Act (pipelines + agents)\n- **Moat**: Continuity Layer (memory, entity graph, workflow intelligence)\n- **Ecosystem Purpose**: Capability fabric, knowledge sharing, tool-to-tool communication, agent communication\n\n## Stages\n\n### Stage 1 — Parallel Deep-Dive Architecture (5 subagents)\n\nEach subagent owns one architectural domain and produces a detailed specification section.\n\n| Subagent                     | Domain                              | Deliverable                                                                                                                |\n| ---------------------------- | ----------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |\n| Arch_L1_IdentityIngress      | Identity Layer + Ingress Layer      | Complete API contracts, auth flows, tenant resolution, transport protocols, routing, rate limiting, discovery              |\n| Arch_L2_CapabilityOODA       | Capability Layer + OODA Runtime     | Capability registry, runtime routing, context assembly, ADK, agent runtime, execution routing, OODA phase mapping          |\n| Arch_L3_ContinuityGovernance | Continuity Layer + Governance Layer | Spine architecture, memory lifecycle, entity graph, knowledge, normalizer, governance rules, approval gates, HITL          |\n| Arch_L4_ProviderFabric       | Provider Fabric + Adapter Pattern   | Outbound/inbound adapters, Nango, MCP, Native, credential wall, tool-to-tool communication                                 |\n| Arch_L5_EcosystemFabric      | Ecosystem Architecture + SDK        | Capability fabric model, knowledge sharing protocol, agent-to-agent communication, SDK variants, ecosystem app composition |\n\n### Stage 2 — Cross-Cutting Concerns (3 subagents)\n\n| Subagent        | Domain                            | Deliverable                                                                         |\n| --------------- | --------------------------------- | ----------------------------------------------------------------------------------- |\n| Arch_Security   | Security Model                    | Zero-trust boundaries, P0/P1 posture, tenant isolation, audit model                 |\n| Arch_DataModel  | Data Model + Entity Relationships | Complete entity relationship diagram across all layers, spine schema, memory schema |\n| Arch_Deployment | Deployment Architecture           | Service topology, Cloudflare Workers topology, D1 schema, CI/CD, local dev          |\n\n### Stage 3 — Integration (1 subagent)\n\nMerge all outputs into a single canonical document: `INTEGRATEWISE_ARCHITECTURE_v2.0.md`\n\n## Key Design Decisions\n\n1. **Twin is NOT a separate entity** — it is ambient context inside the Capability + Continuity layers\n2. **Onboarding is a distinct flow** — separate from operational OODA, pipeline-heavy with agent guidance\n3. **MCP is a transport** — sits in Ingress, not Capability\n4. **Ecosystem = Capability Fabric** — not lightweight apps, but interoperating capabilities\n5. **Agent/pipeline boundary** — agents handle uncertainty, pipelines handle certainty\n6. **HITL is at the Decide phase** — irreducible human agency\n7. **Moat = Continuity Layer** — time-accumulated memory, entity graph, workflow intelligence\n\n## Output Format\n\nEach subagent produces Markdown with:\n\n- ASCII diagrams where helpful\n- TypeScript interface definitions\n- SQL schema where relevant\n- Flow descriptions\n- Security boundary annotations\n\n## Final Deliverable\n\n`INTEGRATEWISE_ARCHITECTURE_v2.0.md` — the single canonical architecture document that supersedes all prior documents.\n"}