{"slug":"documentation/DOCUMENTATION_COMPLETION_MANIFEST","title":"Documentation Completion Manifest","section":"documentation","sectionLabel":"Documentation","status":"current","type":"document","path":"documentation/DOCUMENTATION_COMPLETION_MANIFEST.mdx","bytes":8484,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n**Status:** Current documentation control index — derived from frozen authority\n**Date:** July 29, 2026\n**Purpose:** Make the final documentation set discoverable, distinguish governing\ndocuments from evidence and history, and record the remaining documentation\nclosure checks.\n\n## 1. Authority order\n\n1. [`AGENTS.md`](../../AGENTS.md)\n2. [`ARCHITECTURE_LOCK.md`](ARCHITECTURE_LOCK.md)\n3. [`IMPLEMENTATION_CONTRACT_v1.1.md`](IMPLEMENTATION_CONTRACT_v1.1.md) for\n   later implementation detail\n4. [`CONSOLIDATED_PRODUCT_PLATFORM_CONTRACT_v1.2.md`](CONSOLIDATED_PRODUCT_PLATFORM_CONTRACT_v1.2.md)\n   for the reconciled runtime, environment, marketplace and frontend/API\n   implementation standard\n5. [`SOURCE_PACK_RECONCILIATION_2026-07-28.md`](SOURCE_PACK_RECONCILIATION_2026-07-28.md)\n   for source classification, conflict resolution and deliberate exclusions\n6. [`FOUR_BUTTONS.md`](FOUR_BUTTONS.md) and [`TWIN_BEHAVIOR.md`](TWIN_BEHAVIOR.md)\n   for specialized OODA controls and Silent Twin behavior\n7. [`TENANT_SPINE_FORTRESS_OPERATIONAL_FLOW_MODEL.md`](TENANT_SPINE_FORTRESS_OPERATIONAL_FLOW_MODEL.md)\n   for the corrected four-flow, Operational Spine, Fortress, search, promotion,\n   retention and environment lifecycle\n8. [`IW_SPINE_NETWORK_PLUGIN_AND_MCP_MARKETPLACE_CONTRACT.md`](IW_SPINE_NETWORK_PLUGIN_AND_MCP_MARKETPLACE_CONTRACT.md)\n   for Plugin Directory and MCP Marketplace publication, embedded host UI,\n   browser Workbench, discovery and connection composition\n9. Approved implementation and release evidence, only where it does not\n   conflict with the sources above\n\nNo presentation, conversation export, prototype, provider documentation, or\nhistorical architecture file may redefine the frozen product or platform.\n\n## 2. Final documentation coverage\n\nThe primary derived implementation handoff is\n`CONSOLIDATED_PRODUCT_PLATFORM_CONTRACT_v1.2.md`. The detailed documents below\nsupport it; none overrides the frozen authority order.\n\n| Coverage                                  | Governing / primary documents                                                                                                                                                                                                 | Required use                                                                                                                             |\n| ----------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |\n| Product and Workbench                     | `ARCHITECTURE_LOCK.md`, `FOUR_BUTTONS.md`, `TWIN_BEHAVIOR.md`, `WORKBENCH_MATRIX.md`, `WORKBENCH_ROLE_CAPABILITY_MAP.md`, `FRONTEND_PLATFORM_API_AND_DISCOVERY_SPEC.md`                                                       | Product design, UX, role/view composition, Gateway wiring and discovery                                                                  |\n| Platform and runtime                      | `IMPLEMENTATION_CONTRACT_v1.1.md`, `PLATFORM_ARCHITECTURE.md`, `CANONICAL_PLATFORM_ARCHITECTURE.md`, `RUNTIME_SUBSTRATE_AND_SURFACE_CONTRACT.md`                                                                              | Service boundaries, runtime guarantees, data ownership, surface contracts                                                                |\n| Spine, projection, and governance         | `TENANT_SPINE_FORTRESS_OPERATIONAL_FLOW_MODEL.md`, `ADAPTIVE_SPINE_MODEL_v1.md`, `PROJECTION_CONSTITUTION.md`, `GOVERNANCE_CONSTITUTION.md`, `EXECUTION_CONSTITUTION.md`, `PLATFORM_PRODUCT_DATA_AND_PROJECTION_REFERENCE.md` | Four flows, schema, Operational/Fortress split, connector-to-Spine mapping, search/read paths, canonical writes, approvals and retention |\n| Connectors and Marketplace                | `IW_SPINE_NETWORK_PLUGIN_AND_MCP_MARKETPLACE_CONTRACT.md`, `CONNECTOR_CONSTITUTION.md`, `CAPABILITY_CONSTITUTION.md`, `PRODUCT_PLATFORM_BOUNDARY_AND_GO_LIVE_STANDARD.md`                                                     | Plugin/MCP publication lanes, host UI, browser Workbench, connector lifecycle, discovery and activation                                  |\n| Engineering agent work                    | `SPINE_INTELLIGENCE_AGENT.md`, `PRODUCT_PLATFORM_BOUNDARY_AND_GO_LIVE_STANDARD.md`                                                                                                                                            | Bounded code proposals, testing, approval, execution                                                                                     |\n| Release and verification                  | `MASTER_EXECUTION_PLAN.md`, `docs/wiki/20-release-readiness-and-verification-evidence.md`                                                                                                                                     | Environment gates, launch evidence, stop-ship checks                                                                                     |\n| Full source-traced company set            | `docs/wiki/README.md`, `docs/wiki/00-master-canon-and-source-registry.md`, `docs/wiki/22-source-traceability-appendix.md`                                                                                                     | Internal knowledge, Coda publishing, source traceability                                                                                 |\n| Supplied attachment/source reconciliation | `SOURCE_PACK_RECONCILIATION_2026-07-28.md`                                                                                                                                                                                    | Exact duplicates, source authority, adopted decisions, superseded claims, archive treatment and sensitive exclusions                     |\n\n## 3. Required documentation for every delivery\n\nEvery capability, connector, MCP channel, coding-agent change, and Product\nsurface must include:\n\n1. Owner and bounded responsibility.\n2. Entry, input, output, state ownership, authority boundary, and failure path.\n3. Development readiness, Platform release readiness, and Customer activation\n   readiness.\n4. Identity, consent, credential, tenant, and audit requirements.\n5. Test and verification evidence, rollback/removal conditions, and documentation\n   updates.\n\n## 4. Documentation migration state\n\nThe July 29 lifecycle reconciliation is complete at the authority and active\nhandoff level:\n\n- Flow A/B/C/D and Flow D precedence are documented;\n- Operational Spine is D1/KV and Canonical Fortress is Neon;\n- aging is separated from promotion;\n- Triage is separated from authority and write ownership;\n- Twin is the contextual AI Co-worker behavior, not a second runtime;\n- Development, Customer Zero and Customer Production are isolated;\n- Workers for Platforms is optional for isolated customer/agent code, not the\n  default multi-tenant Platform topology;\n- historical, extracted, archive, outbox and status collections are explicitly\n  classified as non-authoritative.\n\nHistorical files retain their original claims for traceability. Their presence\nis not an unresolved canonical contradiction when the file or its collection\nindex routes readers to the governing set.\n\n## 5. Closure state\n\nThe maintained wiki pack and the `docs/frontend-v0` implementation handoff are\ncomplete as indexed document sets. The frontend handoff now includes the work\ninteraction, connector marketplace, Customer Zero MCP operations, Platform\nmodules, Administration, shared state, responsive and testing contracts.\n\n“Complete documentation” means the required responsibility and communication\ncontracts exist and route to frozen authority. It does not mean every documented\nruntime feature is implemented or deployed. Implementation and live-environment\nclaims still require the evidence gates in `MASTER_EXECUTION_PLAN.md`.\n\n## 6. Historical material\n\nOlder architecture snapshots, implementation plans, generated exports, and\nconversation transcripts are retained for rationale and evidence only. When they\ndisagree with the authority order above, label them **Historical** or\n**Superseded** rather than silently blending their claims into current work.\n"}