{"slug":"operations/20-release-readiness-and-verification-evidence","title":"20 — Release Readiness and Verification Evidence","section":"operations","sectionLabel":"Operations","status":"current","type":"document","path":"operations/20-release-readiness-and-verification-evidence.mdx","bytes":2758,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n**Status:** Active launch control\n\n**Hard freeze:** 2026-07-29\n\n**Production go-live target:** 2026-07-30\n\n## Required before merge\n\n- browser identity has one configured authority;\n- Gateway rejects missing or conflicting user/account/tenant context;\n- connector records require provider workspace, Spine Connection, and compatible\n  schema evidence;\n- stale bindings fail closed in every reader;\n- Pipeline is the only canonical writer;\n- public MCP tool inventory is exactly nineteen;\n- approval and Hermes cannot be bypassed;\n- credentials never enter browser, Spine, prompts, logs, or repo;\n- projections never silently fall back to demo data;\n- cross-tenant read/write tests pass;\n- migration, rollback, and compatibility tests pass.\n\n## Required before production cutover\n\n- Clerk production Organisation and callback configuration;\n- Vercel Workbench build and authenticated route verification;\n- Cloudflare Gateway, OAuth, MCP, Pipeline, connector, queue, and service bindings;\n- Neon, D1, KV, R2, retrieval, and migration readiness;\n- Nango production provider configurations;\n- DNS, TLS, health, status, and support endpoints;\n- Customer Zero golden journey and evidence pack;\n- stale, repair, revoke, provider-failure, and callback-loss tests;\n- monitoring, alerts, ownership, incident response, and rollback drill;\n- privacy, terms, security, support, and deletion/export paths.\n\n## Stop-ship list\n\n- Descope selected for browser sessions while Clerk is configured;\n- no authoritative account and tenant resolution;\n- browser-supplied identity accepted;\n- connector operational without complete binding and schema tuple;\n- stale connector visible as connected or usable;\n- direct UI, Twin, MCP, connector, or projection write to Neon;\n- public MCP drift;\n- no approval token for a consequential action;\n- Hermes bypass;\n- production endpoint unhealthy;\n- no clean rollback target;\n- any cross-tenant access.\n\n## Evidence record\n\nEach release candidate records:\n\n- commit, package, build, deployment, and migration IDs;\n- environment and configuration version;\n- test suite and negative-case results;\n- Customer Zero journey evidence;\n- connector and schema binding references;\n- audit correlation IDs;\n- security and legal review;\n- known exceptions with owner and expiry;\n- release decision and rollback target.\n\n## Acceptance statement\n\nThe launch is accepted when a clean verified user enters the correct tenant,\ninstalls a launch connector, completes provider auth, binding, schema validation,\ninitial sync, and Pipeline promotion, sees canonical Integration Manager and\nWorkbench state, executes one approved action through Hermes, and observes stale\nor cross-tenant state fail closed.\n"}