Split out of #3541 at close-out (2026-07-30): Phase 0 / Phase 1 / Phase 2 D8+D9 shipped and verified; D10 is the one remaining framework-side item of Phase 2, and it is a design item, not a code item.
What ADR-0105 D10 reserves
A spec-level pattern for the SAP material-master / 用友-金蝶 distribution shape: an object may declare layered governance — group-level template rows (platform-global or group-org-owned, read-shared) plus per-org override rows linked to the template, with a resolution rule (org override wins).
The ADR deliberately reserves the concept only. The mechanics are explicitly deferred to a follow-up ADR:
- linkage field between override and template rows;
- resolution in the read path vs a view layer;
- distribution policies: 集团统管 / 分级 / 自由;
- how the layered read composes with the D2 union wall and D5 stamping (a template row is readable across the wall by design — the first deliberate exception to
organization_id IN accessible_org_ids, which is exactly why it needs its own decision record).
Status
None of ADR-0106…0113 is that ADR (verified during the 2026-07-30 re-evaluation of #3541). Per ADR-0049 discipline, nothing ships before the decision record exists — the concept is reserved, not licensed.
Definition of done
The follow-up ADR is proposed (own proposal PR + own tracking issue, per convention — as ADR-0105 itself did via #3499 → #3541). This issue closes when that tracking issue exists and takes over.
Refs: ADR-0105 §D10, #3541 (close-out), objectstack-ai/cloud#874 (master-data distribution management is the commercial face and stays cloud-side per the repo split).
Split out of #3541 at close-out (2026-07-30): Phase 0 / Phase 1 / Phase 2 D8+D9 shipped and verified; D10 is the one remaining framework-side item of Phase 2, and it is a design item, not a code item.
What ADR-0105 D10 reserves
A spec-level pattern for the SAP material-master / 用友-金蝶 distribution shape: an object may declare layered governance — group-level template rows (platform-global or group-org-owned, read-shared) plus per-org override rows linked to the template, with a resolution rule (org override wins).
The ADR deliberately reserves the concept only. The mechanics are explicitly deferred to a follow-up ADR:
organization_id IN accessible_org_ids, which is exactly why it needs its own decision record).Status
None of ADR-0106…0113 is that ADR (verified during the 2026-07-30 re-evaluation of #3541). Per ADR-0049 discipline, nothing ships before the decision record exists — the concept is reserved, not licensed.
Definition of done
The follow-up ADR is proposed (own proposal PR + own tracking issue, per convention — as ADR-0105 itself did via #3499 → #3541). This issue closes when that tracking issue exists and takes over.
Refs: ADR-0105 §D10, #3541 (close-out), objectstack-ai/cloud#874 (master-data distribution management is the commercial face and stays cloud-side per the repo split).