Unclassified
26 · Runtime Wiring
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.
What Is Actually Wired
This page shows the real dependency graph, not the intended one. Orphaned paths are listed explicitly.
apps/web ──→ services/gateway ──→ projection? vs direct composition?
(G-02 evidence)
apps/docs ─────────────────────────→ Mintlify (this site)
services/spine ←── Loader ←── Normalizer ←── Pipeline (four flows)
│
└── Governed Writer (only path to Spine) (G-03)
services/ai ──→ AI Gateway ──→ model routing
│
├── ADK middleware (orphan — see G-07)
└── Twin (twin:{userId}) → AI Workbench projection
MCP Pool ──→ Capability Fabric ──→ Governance ──→ Hermes ──→ provider
(routing boundary) (what can) (may I?) (execute)
If a service is not in this graph, it is either not yet surveyed or it is an orphaned path awaiting removal — see Codebase Alignment G-07.
Live vs Orphaned
| Path | Status | Evidence |
|---|---|---|
| Gateway → Projection Engine as sole composition | Target (G-02) — partial | 002-shared-workbench-sole-composed-output vs current mixed paths |
| Loader → Governed Writer → Spine | Target (G-03) | Four-flow contracts; direct Spine writes still present |
| ADK middleware → Capability Fabric | Orphan — requires wiring evidence | G-07 in gap register |
| MCP Pool → Capability Fabric → Hermes | Governed route — MCP never bypasses Governance | MCP routing boundary |
Data Paths
- Read: External Systems → Loader → Normalizer → Pipeline → Governed Writer → Spine → Projection → Human/AI Workbench.
- Write: Work → Capability Fabric → Governance → Hermes → External System → Re-ingest → Verify → Reconcile → Spine → Rehydrate.
Both are traced. See Contracts.
Where to Go Next
<CardGroup cols={2}>Gap register and remediation sequence.
Schemas, commands, events, and authority that wiring must obey.
The product view of the same wiring.