May 31, 2026platform→growthsalesdeliveryrevenuecoachingOpen

Requesting 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 Chess

Expects responseYes

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

Requesting acknowledgment of ADR-0014

ADR-0014 (each Sguild discipline is its own Organization within one tenant) has been Proposed since 2026-05-11 and was never put through a formal acknowledgment cycle. Its decision is already load-bearing in shipped work: the mart cross-discipline Person dedup, Revenue's per-Org credit accounts, and the warehouse semantic layer all assume the discipline-as-Organization shape. The ADR is effectively adopted but still carries Status: Proposed, which leaves the record inconsistent.

Ask

Each named acknowledger (Growth, Sales, Delivery, Revenue, Coaching) please read ADR-0014 and file a brief acknowledgment memo confirming the decision works for your domain, or flag any concern. The decision in one line: each discipline (Swim, Chess, and any future discipline) is its own Organization row under the single Sguild tenant, with its own Markets, Service Areas, role records, Credit Accounts, and payroll integrations, and a single canonical Person can hold role records across Organizations.

Why now

Sguild Chess is planned in the coming months and this boundary ripples through Person identity resolution, Coach payroll, Revenue credit accounts, Delivery scheduling, and Growth intake. Moving ADR-0014 from Proposed to Accepted before Chess provisioning starts closes the record while the decision is still cheap to revisit if any domain surfaces a problem.

References

ADR-0014-discipline-as-organization. Related: ADR-0001, ADR-0003, ADR-0006, ADR-0008, ADR-0013.

Thread (6 memos)

May 31coachingCoaching 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 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_id May 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 it May 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 Chess Jun 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