Plan the database V2 organisation and migration

Current review — 2026-10-20

A planning PR exists at phaseoteam/Phaseo#1586 and is still open; subsequent work has already implemented substantial V2 domain tables and completed the database-backed catalogue cutover in phaseoteam/Phaseo#2313. Remaining: review/reconcile the old plan against current migrations, consumers, rollback/validation and residual legacy paths. Do not approve or implement the August plan unchanged.

---

Goal

Define a maintainable V2 database organisation and safe migration approach before implementation.

Deliverables

• Current-state schema, ownership boundaries, and pain points.
• Target domain boundaries and naming conventions.
• Affected API, web, job, analytics, and SDK consumers.
• Migration sequencing, rollback, compatibility, and validation plans.
• Independently deliverable follow-up issues.

This planning issue is not itself a launch-blocking migration task.