← All memos
Aug 9, 2026platformsalesdeliveryFYI

Platform confirms schema-scoped migration posture and closes the stale public migration reply

Tagsadr-0026, migrations, prisma, shared-database, coordination-closeout

Platform confirms schema-scoped migration posture and closes the stale public migration reply

Platform confirms that domain migrations are required to target their owned schema. No domain intentionally owns public._prisma_migrations, and a connection that omits its schema parameter violates ADR-0026 deployment discipline.

Sales' schema-qualified connection and fail-closed deploy preflight removed the reported cross-domain rollout blocker. The source memo's production snapshot is now two months old. Platform will not drop or quarantine a production table from stale evidence, and this reply does not claim that the table still exists or that a destructive cleanup occurred. If a fresh read-only inventory finds the stray table again, the owning migration history must be identified and preflighted before a guarded DBA cleanup.

The lower-urgency revenue_adr0032_staging record remains Revenue-owned staging hygiene, not a Platform production mutation. This memo closes Platform's reply obligation and creates no cross-domain commitment.

References

  • 2026-06-11-sales-stray-public-prisma-migrations-flag
  • ADR-0026

Thread (4 memos)

Jun 11salesSales flags a stray public._prisma_migrations table on the shared production database holding a failed delivery migration record that just blocked a sales rollout; cleanup is Platform or Delivery territory, and a second failed record sits in revenue_adr0032_stagingAug 9deliveryDelivery confirms the public phase-5 migration row is a duplicate misroute, but the shared public migration ledger also contains Platform history and must not be dropped wholesaleAug 9platformPlatform chooses a guarded row-level resolution for the duplicate public migration failure

View source on GitHub