{"slug":"developers/19-implementation-plan-and-repository-mapping","title":"19 — Implementation Plan and Repository Mapping","section":"developers","sectionLabel":"Developers","status":"unclassified","type":"document","path":"developers/19-implementation-plan-and-repository-mapping.mdx","bytes":3553,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n**Status:** Repository evidence snapshot as of 2026-07-27\n\n## Canonical ownership map\n\n| Responsibility                              | Repository owner                                       |\n| ------------------------------------------- | ------------------------------------------------------ |\n| App Router Workbench                        | `apps/web/`                                            |\n| Public control, identity, tenant resolution | `services/gateway/`                                    |\n| Public nineteen-tool MCP                    | `services/mcp-connector/`                              |\n| Internal capability registry and routing    | `services/mcp-pool/`                                   |\n| Connector catalog and provider transport    | `packages/connectors/`, connector services             |\n| Load and normalisation                      | `services/loader/`, `services/normalizer/`             |\n| Triage, promotion, canonical writes         | `services/pipeline/`                                   |\n| Canonical Spine reads                       | `services/spine/`                                      |\n| SharedWorkbench composition                 | `packages/projection-engine/`                          |\n| Governance and approved execution           | `services/govern/`, `services/hermes/`                 |\n| Knowledge and retrieval                     | `services/knowledge/`                                  |\n| Twin and agent runtime                      | `services/intelligence/`, `services/iw-agent-runtime/` |\n| Role composition                            | `packages/workbench-config/`                           |\n| Canonical entity contracts                  | `packages/spine-entities/`, `packages/spine-schema/`   |\n\n## Component validity contract\n\nEvery surface, service, package, agent, capability, connector, and storage plane\nmust declare:\n\n- reason to exist and owner;\n- upstream entry and input contracts;\n- bounded responsibility;\n- output and downstream consumer;\n- state ownership and prohibited responsibilities;\n- authority boundary;\n- failure, retry, and reconciliation;\n- observability;\n- lifecycle and removal condition.\n\nThe disposition choices are:\n\n`KEEP · WIRE · MERGE · DEPRECATE · REMOVE`\n\n## Current connector-binding gap\n\nThe approved binding ADR and plan specify strict `connector_bindings` and\n`connector_schema_bindings`. Repository search shows these records in design and\nplan documents, but not in the runtime migrations. Existing paths include\ntenant-only integration state, provider-name arrays, and older Supabase-backed\nconnection reads. Runtime implementation and reader migration remain release\nwork.\n\n## Pre-go-live workstreams\n\n1. Shared environment and secret management.\n2. Canonical, operational, memory, object, cache, and retrieval state boundaries.\n3. Base Spine and additive schema contracts.\n4. Schema creation and expansion algorithm.\n5. Connector registry and Integration Manager.\n6. OAuth and direct connector framework.\n7. Public Spine MCP and package.\n8. MCP Pool and capability discovery/resolution.\n9. ADK, skills, plugins, agents, and model policy.\n10. Frontend tables and frontend-to-backend projection mapping.\n11. Customer Zero Spine Network.\n12. End-to-end negative and recovery verification.\n\n## Implementation order\n\nUse the frozen Master Execution Plan. Do not expand public surface area while\nidentity, binding, promotion, projection, Governance, or reconciliation remains\nincomplete.\n"}