{"slug":"implementation/runtime-wiring","title":"26 · Runtime Wiring","section":"implementation","sectionLabel":"Implementation","status":"unclassified","type":"document","path":"implementation/runtime-wiring.mdx","bytes":2777,"description":"What imports what, what invokes what, live vs orphaned paths, startup/runtime wiring, execution routes, and data paths — including ADK middleware orphan and MCP Pool routing evidence.","updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n## What Is Actually Wired\n\nThis page shows the **real dependency graph**, not the intended one. Orphaned paths are listed explicitly.\n\n```text\napps/web  ──→  services/gateway  ──→  projection?  vs  direct composition?\n                                     (G-02 evidence)\napps/docs ─────────────────────────→  Mintlify (this site)\n\nservices/spine ←── Loader ←── Normalizer ←── Pipeline (four flows)\n     │\n     └── Governed Writer (only path to Spine)  (G-03)\n\nservices/ai  ──→ AI Gateway  ──→ model routing\n   │\n   ├── ADK middleware  (orphan — see G-07)\n   └── Twin (twin:{userId})  →  AI Workbench projection\n\nMCP Pool  ──→  Capability Fabric  ──→  Governance  ──→  Hermes  ──→  provider\n  (routing boundary)        (what can)     (may I?)       (execute)\n```\n\n\nIf a service is not in this graph, it is either not yet surveyed or it is an orphaned path awaiting removal — see [Codebase Alignment](/implementation/codebase-alignment) G-07.\n\n\n## Live vs Orphaned\n\n| Path | Status | Evidence |\n|---|---|---|\n| Gateway → Projection Engine as sole composition | Target (G-02) — partial | `002-shared-workbench-sole-composed-output` vs current mixed paths |\n| Loader → Governed Writer → Spine | Target (G-03) | Four-flow contracts; direct Spine writes still present |\n| ADK middleware → Capability Fabric | Orphan — requires wiring evidence | G-07 in gap register |\n| MCP Pool → Capability Fabric → Hermes | Governed route — MCP never bypasses Governance | MCP routing boundary |\n\n## Data Paths\n\n* **Read:** External Systems → Loader → Normalizer → Pipeline → Governed Writer → Spine → Projection → Human/AI Workbench.\n* **Write:** Work → Capability Fabric → Governance → Hermes → External System → Re-ingest → Verify → Reconcile → Spine → Rehydrate.\n\nBoth are traced. See [Contracts](/implementation/contracts).\n\n## Where to Go Next\n\n<CardGroup cols={2}>\n  \n    Gap register and remediation sequence.\n  \n  \n    Schemas, commands, events, and authority that wiring must obey.\n  \n  \n    The product view of the same wiring.\n  \n</CardGroup>\n"}