Evidence level: historically reviewed source and owner proposals; not freshly tested or certified for production.
Design and implementation invariants
- Schema migrations must be additive/compatible when required and must use explicit owner-scoped database authority.
- Sensitive deployment templates and production environment configurations require security-owner review, not automatic migration from the monolith.
- Build/release tooling is distinct from actual database mutation or application services.
Verification still required
- Verify transactional behavior and failure modes against an authorized disposable multi-node YSQL fixture.
- Review live environment, schema grants, rollback and release sequencing before any production migration.
How to update
When the owner changes implementation or contract behavior, update this page and the relevant service interfaces. For cross-service changes, also update the platform interface map or decision register. State the actual verification performed; do not inherit historical pass claims without fresh evidence.