19 — Implementation Plan and Repository Mapping
Status: Repository evidence snapshot as of 2026-07-27
Canonical ownership map
| Responsibility | Repository owner |
|---|---|
| App Router Workbench | apps/web/ |
| Public control, identity, tenant resolution | services/gateway/ |
| Public nineteen-tool MCP | services/mcp-connector/ |
| Internal capability registry and routing | services/mcp-pool/ |
| Connector catalog and provider transport | packages/connectors/, connector services |
| Load and normalisation | services/loader/, services/normalizer/ |
| Triage, promotion, canonical writes | services/pipeline/ |
| Canonical Spine reads | services/spine/ |
| SharedWorkbench composition | packages/projection-engine/ |
| Governance and approved execution | services/govern/, services/hermes/ |
| Knowledge and retrieval | services/knowledge/ |
| Twin and agent runtime | services/intelligence/, services/iw-agent-runtime/ |
| Role composition | packages/workbench-config/ |
| Canonical entity contracts | packages/spine-entities/, packages/spine-schema/ |
Component validity contract
Every surface, service, package, agent, capability, connector, and storage plane
must declare:
- reason to exist and owner;
- upstream entry and input contracts;
- bounded responsibility;
- output and downstream consumer;
- state ownership and prohibited responsibilities;
- authority boundary;
- failure, retry, and reconciliation;
- observability;
- lifecycle and removal condition.
The disposition choices are:
KEEP · WIRE · MERGE · DEPRECATE · REMOVE
Current connector-binding gap
The approved binding ADR and plan specify strict connector_bindings and
connector_schema_bindings. Repository search shows these records in design and
plan documents, but not in the runtime migrations. Existing paths include
tenant-only integration state, provider-name arrays, and older Supabase-backed
connection reads. Runtime implementation and reader migration remain release
work.
Pre-go-live workstreams
- Shared environment and secret management.
- Canonical, operational, memory, object, cache, and retrieval state boundaries.
- Base Spine and additive schema contracts.
- Schema creation and expansion algorithm.
- Connector registry and Integration Manager.
- OAuth and direct connector framework.
- Public Spine MCP and package.
- MCP Pool and capability discovery/resolution.
- ADK, skills, plugins, agents, and model policy.
- Frontend tables and frontend-to-backend projection mapping.
- Customer Zero Spine Network.
- End-to-end negative and recovery verification.
Implementation order
Use the frozen Master Execution Plan. Do not expand public surface area while
identity, binding, promotion, projection, Governance, or reconciliation remains
incomplete.