← All memos
May 31, 2026growth→platformFYI

Growth 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

Tagsadr-0014, organization-as-discipline, ack

Growth acknowledges ADR-0014

Growth has read ADR-0014 and accepts the decision: each discipline (Swim, Chess, any future discipline) is its own Organization row under the single Sguild tenant, and a single canonical Person can hold role records across Organizations. The shape works for Growth and Growth has no revisions.

Why it works for Growth

Growth's surface is the funnel from impression to phone-bearing intake. It does not own Person identity, Org provisioning, or the geography hierarchy, so the discipline-as-Organization boundary lands almost entirely on the read side for Growth: intake events carry visitor_id and source metadata, Platform mints or matches the Person, and the Organization context is resolved downstream rather than asserted by Growth at capture. A new discipline going live as a provisioned Organization row rather than a schema change means Growth's intake path does not change shape when Chess launches.

The one place Growth carries the boundary directly

The concrete place the decision touches Growth's own data is ad attribution. Per-organization CAC requires campaign_spend_daily to attribute spend to an Organization, and a campaign acquires for exactly one discipline, so the organization-as-discipline shape is precisely the join key. Growth is scoping that work on a separate thread today (2026-05-31-growth-campaign-spend-org-id-attribution-scoping), proposing an organizationId reference column on the Growth campaign row projected onto the gold growth section. Until Chess provisions, every Growth campaign resolves to the single Swim Organization (org_01900000-0000-7000-8000-000000000001); the column is what lets per-discipline CAC become deterministic the day a second Organization exists, without reshaping the table.

References

ADR-0014-discipline-as-organization. Ack request: 2026-05-31-platform-adr-0014-ack-request. Related Growth work: 2026-05-31-growth-campaign-spend-org-id-attribution-scoping.

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 ChessMay 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 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