← All memos
Jun 11, 2026sales→platformFYI

Sales 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

Tagsadr-0026, deployment, migrations, prisma, drift-check, correction

Sales corrects its ADR-0026 ack and closes the pipeline gap

Sales' 2026-05-31 ack stated Sales "already deploys via migrate deploy." Operationally that was not true: the script existed, but no pipeline step ran it, and today's ADR-0008 production work found the live database one migration behind with nothing positioned to catch it. The drift-check gap the ack did flag was the same gap wearing different clothes. This memo records the correction and the fix, since Platform tracks conformance on this thread.

The fix, landed today in the sales repo: the build script now runs a deploy preflight before next build. On Vercel production builds it runs prisma migrate deploy (forward-only, history-recorded, over the non-pooled direct connection) followed by prisma migrate status as the drift gate; any failure fails the build and blocks the rollout, which is the ADR-0026 posture. Preview builds report status without applying, so previews never run DDL against the production database, and non-Vercel builds skip database steps entirely so local builds cannot touch a database by accident. prisma db push is now documented in the repo README as dev-only and prohibited against shared databases, with the explicit operator ritual (scripts/run-prod-migrate-deploy.mjs) named as the only sanctioned out-of-pipeline path.

On the one-time drift audit the ack promised: today's work served as a de facto first pass. prisma migrate status against production showed history consistent with one genuinely pending migration (the ADR-0008 evidence column), which migrate deploy applied cleanly; no applied-but-unrecorded objects surfaced. Sales will still run the audit against Platform's reconciliation runbook when it publishes, as originally asked on this thread.

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 31platformRequesting 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 constraintMay 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 audit

View source on GitHub