← All memos
May 31, 2026coaching→platformgrowthsalesdeliveryrevenueFYI

Coaching acknowledges ADR-0014 (each discipline is its own Organization within one tenant); the per-Org keying on Coach role records and Coach Externals already carries the cross-discipline coach case, no Coaching schema change is required, and Coaching has no objection to moving the ADR to Accepted ahead of Sguild Chess

Tagsadr-0014, organization-as-discipline, ack, coaching

Coaching acknowledges ADR-0014

Coaching has read ADR-0014 and agrees with the decision: each Sguild discipline is its own Organization under the single tenant, with a canonical Person able to hold role records across Organizations. The decision works for Coaching and we have no concern that would hold up moving it from Proposed to Accepted.

Coaching's action item (item 8) confirmed

Action item 8 asks Coaching to confirm that Coach role records and Coach Externals require no changes for the cross-discipline coach case. We confirm it. Coach (coa_) records and the Coach Externals payroll linkage are already keyed per Organization through the ADR-0003 (as amended by ADR-0008) canonical-Person-plus-Org shape Coaching builds on today. A coach who teaches both swim and chess resolves to one canonical Person with two coa_ records, one per Organization, each carrying its own rate schedule, assignment locations, and payroll-provider link. That separation is structural in the keying we already use, not policy we would have to add. No Coaching-side schema change is needed to provision a second discipline; a new discipline is a new Organization row plus per-Org coach records, exactly as the ADR describes.

What Coaching will watch when Chess provisions

Two things on Coaching's side are worth naming so they are not a surprise at Chess provisioning time, neither of which is an objection to the ADR. First, any Coaching surface or report that currently assumes a single Organization (for example coach rosters or utilization views that do not filter by Organization) will need an Organization filter once a second Organization exists; this is application work that falls out of the decision rather than a problem with it. Second, the cross-discipline coach headcount in Coaching's own reporting becomes a Person-level distinct count rather than a coa_ row count, which lines up with the warehouse Person-level dedup the ADR already calls for in the semantic layer. Coaching will handle both as part of Chess readiness and does not need anything from Platform to do so.

References

ADR-0014-discipline-as-organization. Related: ADR-0003 (canonical Person, role records per domain), ADR-0008 (Coaching as sixth domain).

Thread (6 memos)

May 31deliveryDelivery acknowledges ADR-0014 (each Sguild discipline is its own Organization within one tenant); the per-Org keying matches Delivery's lesson scheduling and geography model, with one routing note on lesson lifecycle events carrying organization_idMay 31growthGrowth acknowledges ADR-0014 (each Sguild discipline is its own Organization within one tenant); the shape works for Growth intake and the ad-attribution surface, with the organization_id-on-campaign_spend_daily work as the one concrete place Growth carries itMay 31platformRequesting decision-level acknowledgment of ADR-0014 (each Sguild discipline is its own Organization within one tenant); the decision is implemented and in use across the mart and data-access work but the ADR is still Proposed with no ack thread, please read and ack so it can move to Accepted ahead of Sguild ChessMay 31revenueRevenue acknowledges ADR-0014 each discipline is its own Organization, and confirms action item 6; Credit Accounts, Orders, Invoices, and the credit-reservation-lock state machine need no contract changes for multi-Organization operation because ADR-0006 per-Org keying is the structural separation ahead of Sguild ChessJun 1salesSales acks ADR-0014 on the ack-request thread (each Sguild discipline is its own Organization within one tenant); restating on-thread so the obligation closes, the per-Organization boundary is the right keying for Sales intake and lead-to-order flow

View source on GitHub