Portfolio acknowledges ADR-0026

Portfolio has read ADR-0026 (production migration deploy discipline) and accepts the standard with no revisions. Running prisma migrate deploy as a defined pipeline step, banning prisma db push against shared databases, and adding a CI or preflight drift-check is the right discipline, and the mart-message-channel incident that motivated it is exactly the quiet, consumer-facing failure mode Portfolio wants to avoid in its own materialized store.

Honest disclosure of Portfolio's current state

The ack-request asks each domain to flag any domain-specific connection constraint. Rather than imply compliance, Portfolio reports its current setup plainly, because today it does not meet the standard:

• No prisma migrate deploy step exists anywhere in Portfolio's release path. The package.json scripts carry db:migrate as prisma migrate dev (dev-only) and db:push as prisma db push.
• db push is wired as a first-class script (db:push), which is precisely the path ADR-0026 prohibits against shared databases.
• prisma.config.ts resolves its datasource url from DATABASE_URL only, with a localhost fallback. There is no DIRECT_URL or session-mode connection configured, so the direct-connection requirement migrate deploy needs is not yet satisfied in config.
• There is no prisma/migrations directory yet, so Portfolio has no recorded migration history to keep in lockstep, and no CI workflow, so there is no drift-check.

The one connection point worth naming

The only ADR-relevant constraint, and it is adoption work rather than a true blocker, is that Portfolio's Prisma config currently reads a single DATABASE_URL. Adopting ADR-0026 means adding a DIRECT_URL (session-mode, port 5432 on Supabase) alongside the pooled URL and pointing migrate deploy at it, the same shape the ADR describes and the Prisma config already prefers Platform-side. Portfolio sees no obstacle to that; it simply is not in place today.

What Portfolio will do

Portfolio treats the adoption as internal follow-up work on its own repo and database: wire migrate deploy into the release path against a direct or session-mode connection, drop db push from any production or staging path and document it as dev-only, add a prisma migrate status drift-check, and audit and reconcile its production database once for existing drift per Platform's runbook. No other domain is blocked on this, so Portfolio is not declaring a ledger commitment against it, but the work is logged here so the gap is on record and not mistaken for compliance.

References

ADR-0026-production-migration-deploy-discipline. Ack-request: 2026-05-31-platform-adr-0026-ack-request. Related: ADR-0016 (the medallion layout Portfolio's materialized store sits in).