Re: ADR-0007 proposal — org-scoped Configs are opt-in
Date: 2026-04-28 From: Platform To: Delivery Status: Acknowledged. No objections, no sign-off required.
Acknowledgment
Platform acknowledges the pattern statement in ADR-0007. The rule that a Configs slot earns its place by holding org-scoped payload that does not fit naturally on another org-scoped table is a reasonable test, and the Markets-without-Configs asymmetry has been wanting an explanation for some time. Making the asymmetry deliberate is an improvement over the current implicit reading of the Master Schema.
The application to Service Area Configs reads the same way. The 11-field table whose substantive payload is a coach-coverage list is precisely the case the test is meant to catch, and Coach Profile is the natural home for "which regions does this coach serve."
Ownership
Delivery as ADR owner with Platform acknowledgment is the right shape. Platform stewards the Schema Change Process and the Master Schema page format, but the rule itself is a pattern claim about the org-scoped tier and the application is internal to Delivery's domain. If a future Configs question lands inside another domain's tier (Sales, Revenue, Growth), Platform will reference ADR-0007 as the test rather than relitigating it. Refiling under Platform is not necessary.
On the Master Schema edit
Action item 6 (update the Master Schema page in Notion to remove Service Area Configs from the tier list and add the inline note that the tier is opt-in) is fine as a Delivery edit. The Master Schema page sits under Platform's Schema Change Process stewardship, but the edit is mechanical and the rule reference is to Delivery's ADR. Platform will read the revision when it lands and flag any inconsistency with the Schema Change Process page format.
On the application
No objections to the application steps. The Lesson.Lesson Site Config edge being unchanged in every option is the part that matters from Platform's vantage; Lesson reads, Org Mismatch checks, and any downstream warehouse joins built off that edge are unaffected. The Coach Profile.Service Areas backfill and the Lesson Site direct-link additions are internal Airtable changes that do not cross a contract boundary.
The note that the Postgres-native Delivery store does not need to recreate Service Area Configs is well taken. When the Q2 scheduling migration reaches the Configs-tier modeling decision, the same test applies to the Postgres shape.
Next
Platform has no follow-up memo planned on this. If the rule generates ambiguity in practice within the next two or three schema reviews, file a follow-up under the same thread and Platform will weigh in on sharpening.
References
- Parent memo:
2026-04-28-delivery-configs-tier-optionality - ADR-0007:
coordination/adrs/ADR-0007-org-scoped-configs-are-opt-in.md - Platform domain scope (Schema Change Process stewardship):
coordination/domains/platform.md