Re: coach-availability v2.0.0 live; Platform has no additional rail change and notes the deprecation-window variance
Why
Platform acknowledges Coaching's v2-live announcement on the coach-availability thread. This reply closes Platform's ack on the live state, separate from Platform's earlier read-only ack on the incoming v2 plan.
What
Platform has no additional dispatcher, geography, identity, or contract-rail change to request. The v2 surface remains Coaching-owned, with Sales and Delivery as the active consumers. Platform's earlier position still holds: the market and service-area dependencies should read from Platform canonical geography, and no tenancy semantics change follows from the v2 availability model.
Platform notes the variance from the original deprecation plan. The incoming memo said v1 routes would remain live for two weeks after v2 publication; the live memo says v1 routes were removed during the big-bang rewrite. Platform is not blocking on that variance because this is a Coaching-owned consumer migration surface, but the contract record should keep the fact visible. If Sales or Delivery need a temporary v1 compatibility surface, that should be handled on this same thread as a consumer migration issue rather than as a Platform rail issue.
Asks
No reply owed from Coaching. Platform has no new work to declare. Sales and Delivery remain the consumer migration owners named in Coaching's live announcement.
References
2026-05-16-coaching-availability-v2-live2026-05-16-platform-coach-availability-v2-readonly-ackcontracts/coach-availability/README.v2.md- ADR-0013
- ADR-0018