Unclassified

July 27–30, 2026 Go-Live Runbook

Status: Approved operational runbook

Hard freeze: July 29, 2026

Go-live: July 30, 2026

Accountable Roles

  • Release owner: final go/no-go and rollback authority.
  • Identity owner: Clerk, organizations, OAuth providers, webhooks, and sessions.
  • Web owner: Vercel, environment, domains, build, routes, and observability.
  • Platform owner: Cloudflare Gateway, auth, MCP, bindings, queues, DNS, and
    secrets.
  • Integration owner: Nango, provider apps, bindings, schemas, sync, and
    webhooks.
  • Data owner: Pipeline promotion, Spine integrity, migrations, and projections.
  • Verification owner: Customer Zero evidence, negative tests, and release
    record.

One person may hold multiple roles, but each role has one accountable owner.

July 27 — Decide, Provision, Restore

Identity

  • Freeze Clerk as the only browser identity.
  • Activate the Clerk production instance.
  • Configure app.integratewise.ai, DNS, allowed origins, and redirects.
  • Enable required Organizations and disable personal accounts.
  • Create the Customer Zero organization and verified memberships.
  • Configure only launch-ready sign-in providers.
  • Provision Clerk webhook signing.
  • Remove Descope from production browser configuration.

Web

  • Upgrade the Vercel CLI from 54.18.6 to the current 58.1.0 release with
    pnpm add -g vercel@latest (or npm i -g vercel@latest).
  • Correct the linked Vercel project for the Next.js application.
  • Configure preview environment values.
  • Deploy the release candidate to preview.
  • Verify /sign-in, /sign-up, /onboarding, /marketplace, and
    /workbench.

Platform

  • Restore gateway.integratewise.ai DNS and Worker routing.
  • Restore auth.integratewise.ai and OAuth discovery.
  • Verify CORS, TLS, security headers, rate limits, health probes, and secrets.
  • Confirm Gateway validates Clerk and rejects invalid sessions.
  • Remove email-derived tenant authorization and first-membership selection.
  • Require active organization and canonical membership.

Integration

  • Freeze Nango as the launch credential wall.
  • Verify provider credentials, callbacks, and scopes for golden connectors.
  • Keep legacy Descope outbound adapters disabled.
  • Confirm the connector binding envelope and Pipeline promotion contract.

End-of-day gate: a clean preview session signs in through Clerk and receives
a Gateway-resolved Customer Zero account and tenant.

July 28 — Customer Zero and Failure Proof

  • Run the complete Customer Zero journey for the golden connector set.
  • Verify initial and incremental sync.
  • Verify webhook resolution where applicable.
  • Verify schema binding and canonical Spine promotion.
  • Verify Integration Manager projections.
  • Exercise missing organization, identity override, cross-tenant, revoked
    credential, incompatible schema, failed promotion, and stale repair cases.
  • Capture evidence and fix only launch-blocking defects.
  • Run unit, integration, boundary, and browser tests.
  • Produce release and rollback candidates.

End-of-day gate: Customer Zero passes without bypasses and every negative
case fails closed.

July 29 — Hard Freeze

No new connectors, features, dependencies, architectural changes, or
publication claims.

  • Merge only approved release blockers.
  • Run the complete required test and release suite.
  • Rebuild from the frozen commit.
  • Deploy the final preview candidate.
  • Repeat identity, connector, sync, stale, and tenant-isolation smoke tests.
  • Validate production environment and secret names without printing values.
  • Validate DNS and certificate readiness.
  • Record commit, artifacts, checksums, environments, endpoints, owners,
    evidence, and rollback target.
  • Conduct the go/no-go review.

Freeze output: one signed release record with no open critical or
high-severity launch blocker.

July 30 — Production Cutover

  1. Confirm required providers and status pages are healthy.
  2. Confirm the frozen commit and artifacts.
  3. Promote the web deployment.
  4. Deploy or promote required Cloudflare Workers from the release record.
  5. Confirm DNS and TLS.
  6. Run unauthenticated public-route checks.
  7. Run Clerk sign-in and organization checks.
  8. Run the Customer Zero connector read/sync smoke test.
  9. Verify Spine and Workbench projection results.
  10. Verify MCP discovery and OAuth if included in launch scope.
  11. Monitor identity, HTTP errors, OAuth, sync, queues, schemas, and binding
    failures.
  12. Announce availability only after the smoke gate passes.

Required Release Gates

Identity

  • Production Clerk instance, domain, DNS, redirects, and webhooks are ready.
  • Organizations are required and personal accounts are disabled.
  • Customer Zero membership is verified.
  • Descope browser configuration is absent.
  • Sign-in, refresh, sign-out, and expired-token behavior pass.
  • No email-derived tenant or owner fallback remains.
  • Multi-tab organization behavior uses a fresh authorization token.

Connector and Spine

  • Installation requires verified user, account, and tenant.
  • Provider workspace and opaque credential reference are captured.
  • Schema compatibility and Pipeline promotion pass.
  • A canonical Spine Connection exists before operational state.
  • Initial and incremental synchronization pass.
  • Stale bindings are excluded from all operational and cognitive consumers.
  • Repair, reconnect, and disconnect preserve audit history.

Tenant Isolation

  • Missing membership returns unauthorized.
  • Client identity override is rejected.
  • Cross-tenant binding, sync, and capability requests are rejected.
  • Provider callbacks cannot change tenant ownership.
  • Webhooks resolve to exactly one tenant binding.
  • Audit events contain subject, account, tenant, and correlation ID.

Infrastructure

  • app.integratewise.ai/sign-in succeeds.
  • app.integratewise.ai/marketplace succeeds.
  • gateway.integratewise.ai/health succeeds.
  • OAuth discovery at auth.integratewise.ai succeeds.
  • TLS, CORS, preview/production separation, monitoring, and rollback pass.

Customer Zero

  • Clean-browser sign-in resolves to iw-customer-zero.
  • Golden connector authorization and binding succeed.
  • Schema promotion and canonical Connection succeed.
  • Initial/incremental sync and projection evidence exist.
  • Deliberate stale state fails closed and repair succeeds.
  • No manual data edit or demo fallback is used.

Rollback Triggers

Rollback immediately for identity outage, incorrect tenant mapping,
cross-tenant visibility, credential exposure, incorrect-tenant Spine writes,
widespread route failure, destructive migration, inability to stop connector
execution, Governance/Hermes bypass, or unbounded queue/error growth.

Rollback Sequence

  1. Stop new connector installations and outbound execution.
  2. Preserve logs and correlation evidence.
  3. Roll web to the recorded previous deployment.
  4. Roll affected Workers to recorded versions.
  5. Disable affected provider callbacks or feature flags.
  6. Pause queues if continued work could corrupt state.
  7. Verify identity and tenant isolation after rollback.
  8. Communicate status and the next checkpoint.
  9. Require a new go/no-go record before another cutover.

Final Sign-Off

  • Release owner:
  • Identity owner:
  • Platform owner:
  • Integration owner:
  • Data owner:
  • Verification owner:
  • Frozen commit:
  • Web deployment:
  • Worker versions:
  • Customer Zero evidence:
  • Rollback target:
  • Go/no-go decision:
  • Decision timestamp: