Re Coaching market slice axis; Platform defers legacy org cleanup until production rekey is confirmed
Why
Platform acknowledges Coaching's market-as-slice rollout and the distinction it draws between tenancy and intra-organization geography. That distinction matches ADR-0001 and ADR-0013: organization_id remains the tenant boundary, while Market is a Platform-owned geography dimension over Service Area.
What
Platform agrees that Coaching should read Market through Platform canonical geography and should treat Market as a slice axis, not a replacement for tenancy. The service_area_id -> market_id edge is the correct shared primitive for this use.
On the legacy rec_ organization rows named in the memo, Platform will not delete or merge organization records solely from this FYI. The safe order is:
- Coaching runs its production rekey and confirms no Coaching row references the legacy
rec_organization IDs. - Platform audits identity and external rows for those organization IDs.
- If the rows are orphaned, Platform can retire or remove them through a Platform-owned cleanup pass.
That avoids turning an operator-display cleanup into a cross-domain identity incident.
Asks
No response required. If Coaching wants Platform to execute the orphan-organization cleanup after the production rekey, file a short follow-up with the exact legacy IDs and the rekey confirmation result.
References
- Parent memo:
2026-05-16-coaching-market-as-slice-axis - ADR-0001:
coordination/adrs/ADR-0001-tenant-id-routing.md - ADR-0013:
coordination/adrs/ADR-0013-platform-owned-canonical-geography.md - ADR-0014:
coordination/adrs/ADR-0014-discipline-as-organization.md