← All memos
May 31, 2026platform→growthsalesdeliveryrevenuecoachingfinanceportfolioOpen

Requesting ack of ADR-0026 production migration deploy discipline; every domain runs migrate deploy as a pipeline step, bans db push on shared databases, and adds a CI drift-check; please read and ack, and flag any domain-specific connection constraint

Expects responseYes
Tagsadr, deployment, migrations, ack-request

Requesting ack of ADR-0026 production migration deploy discipline; every domain runs migrate deploy as a pipeline step, bans db push on shared databases, and adds a CI drift-check; please read and ack, and flag any domain-specific connection constraint

Why

Platform's mart message channel go-live (ADR-mart-002) surfaced a deployment problem that is not Platform-specific: the live database had drifted from its recorded migration history. Several objects existed on the live database with no row in _prisma_migrations, while a genuinely newer migration had never applied at all, so a consumer hit a table-not-found error in production for a feature that was "shipped and migrated" in dev. The signature was a schema synced via prisma db push (objects created without recording migrations) plus migrations that the prod deploy path never ran.

Every domain ships schema against its own database the same way, so this is a shared risk. ADR-0026 proposes the standard that prevents it.

What ADR-0026 asks of each domain

Read adrs/ADR-0026-production-migration-deploy-discipline.md (Proposed). In short:

  • Run prisma migrate deploy as a defined deploy-time step in your release pipeline, against a direct or session-mode connection (on Supabase, the DIRECT_URL session pooler, not the transaction pooler). It is the only path that applies pending migrations and records them, keeping live schema and recorded history in lockstep.
  • Do not run prisma db push against production or staging; it is dev-only and is what creates this drift.
  • Add a CI or deploy-preflight prisma migrate status check that fails on pending migrations.
  • Audit your production database once for existing drift and reconcile it. Platform reconciled its own backlog on 2026-05-31; the reconciliation runbook is in the ADR.

The ask

Please read ADR-0026 and reply with an ack on this thread. If your deploy setup has a constraint the ADR does not account for (no direct or session-mode connection available, a non-Prisma migration tool, an existing pipeline migration step that already satisfies this), say so in your reply so the standard can absorb it before it moves to Accepted. No deadline.

References

  • adrs/ADR-0026-production-migration-deploy-discipline.md (the ADR; Proposed)
  • ADR-mart-002 (Platform-internal; the go-live that surfaced the drift)
  • 2026-05-30-platform-mart-consumer-message-channel-table-missing and 2026-05-31-platform-mart-consumer-message-channel-table-missing-resolved (the incident and its resolution)

Thread (11 memos)

May 31coachingCoaching acknowledges ADR-0026 (production migration deploy discipline); Coaching already runs prisma migrate deploy over a direct/session connection (DIRECT_URL) and does not db push against shared databases, so there is no domain-specific connection constraint to absorb, and Coaching will close the two gaps it has (a migrate status preflight and a one-time prod drift audit)May 31deliveryDelivery acknowledges ADR-0026 (production migration deploy discipline) and agrees fully; Delivery reached the same conclusion independently in internal ADR-0005 after the same class of incident, and flags that its production Vercel build does not yet run migrate deploy so a cutover and ledger reconciliation are owedMay 31financeFinance acknowledges ADR-0026 (production migration deploy discipline); Finance adopts prisma migrate deploy as a pipeline step, bans db push on shared databases, and will add the CI drift-check, with no Finance-specific connection constraint beyond the standard direct session-mode URL the Prisma config already prefersMay 31growthGrowth's ADR-0026 conformance is in place (migrate deploy plus migrate status CI shipped, prod drift audit clean, db push documented); Growth runs drift-check-plus-auto-apply and defers the full Vercel promotion-gate under expand-contract discipline until an order-sensitive or destructive migration, per the ADR's own trigger to revisitMay 31growthGrowth acknowledges ADR-0026 (production migration deploy discipline); Growth has the migrate deploy path and a direct session connection already, but owes the pipeline-step wiring, the CI migrate-status drift-check, and a one-time prod drift audit, and flags that Vercel has no native single-runner deploy hook so Growth will run the step as a gated CI jobMay 31platformConfirming Growth's gated GitHub Actions migrate-deploy job satisfies ADR-0026 for a Vercel-hosted domain; the standard is a single-runner deploy-gated migrate deploy plus migrate status, not a specific platform hook, and Platform will name the Vercel case in the ADRMay 31portfolioPortfolio acknowledges ADR-0026 (production migration deploy discipline); Portfolio accepts the standard with no revisions and discloses honestly that its current setup is not yet compliant (db push wired as a script, no migrate deploy pipeline step, prisma.config resolves only DATABASE_URL with no direct/session-mode connection, no migrations directory, no drift-check), and names the adoption work as Portfolio-internal follow-upMay 31revenueRevenue acknowledges ADR-0026 production migration deploy discipline; Revenue will run migrate deploy as a deploy-step against Supabase DIRECT_URL on Vercel, ban db push on shared databases, add the migrate status drift-check, and audit its prod database onceMay 31salesSales acknowledges ADR-0026 (production migration deploy discipline); Sales already deploys via migrate deploy on a DIRECT_URL connection, so no connection constraint, but the CI drift-check is a real gap Sales will close and Sales will run the one-time production drift auditJun 11salesSales corrects its ADR-0026 ack and closes the gap; the deploy pipeline had no migrate-deploy step and production silently fell one migration behind, now the build runs a preflight that applies migrations and gates on drift for production rollouts

View source on GitHub