decision: ADR-0131 C5 — under single, Studio saves are stored organization-scoped today. At the v18 upgrade, are they promoted to the environment, kept behind a compatibility read, or dropped? #22011

Activity

1. objectstack-fleet

   added

   priority:p1High: required for production / M2High: required for production / M2

   needs-user-decisionBlocked on a maintainer decision — do not dispatch; decision cards only, never on a PRBlocked on a maintainer decision — do not dispatch; decision cards only, never on a PR

   target:v18

   domain:engineRetired 2026-10-22, alias of domain:server (engine surface); in-flight cards keep it until they landRetired 2026-10-22, alias of domain:server (engine surface); in-flight cards keep it until they land

   on Oct 6, 2026
2. objectstack-fleet commented on Oct 6, 2026

   

   objectstack-fleetBot

   on Oct 6, 2026

   ContributorAuthor

   More actions

   Ruling: batch #282 item 4 · letter A · maintainer 「同意」 2026-10-06T15:56Z

   Director seat, summon #35, session_01VYToj6PQehTEKNrjGM9akg (GitHub os-zhuang; written as objectstack-fleet[bot] via the relay). Batch #282 was presented in chat with this card's options A / B / C; the maintainer answered 「同意」, which takes the recommendation. Freshness gate: the body (no comments), #15206, #21818 and ADR-0131 D6 / D10 / D13 were re-read before this record. Thread-read: none on this card.

   The ruling

   A. Under single, the organization-scoped sys_metadata rows of the five presentational types (view, dashboard, report, translation, email_template) that Studio saved for the Default Organization (#21818's measurement) are promoted to environment scope by the migration ceremony (C7, #15211). This is the execution of two accepted decisions, not a new direction: D13 retires ADR-0005's organization-scoped write path for these types, so B (a compatibility read of the Default Organization's rows) contradicts it; D10 sanctions deletion only of mirrors (fate 2), and a customer's Studio edit is not a mirror, so C (drop) contradicts it. The promotion is D10's fate 3 applied to the environment as the owner.

   Conflict rule. On a deployment that runs single with more than one organization (#17460 reports it at boot, never refuses), the Default Organization's row promotes; another organization's row of the same name is reported, never guessed (D10 fate 4): the plan lists it with the remedy, and the operator chooses per row.

   Together with: item 3 (#22008, the withdrawal sub-case, fail-closed) and item 5 (#22005, email templates), one ceremony, one rule.

   Execution

   • C7 (feat(objectql,cli): inventory + migration — four fates per object, mirrors deleted only after the id→name rewrite is verified, per-table boot report (ADR-0131 D10) #15211): the migration plan gains the "organization-scoped customization promotion" category with the conflict list.
   • C5 (feat(metadata-core,metadata-protocol,objectql,plugin-security): the sys_metadata family goes tenant-less; the per-organization overlay axis retires; managed content is sealed (ADR-0131 D6/D7/D13) #15206): its retirement proceeds on this premise; no compatibility read is kept.
   • Pointers recorded on feat(metadata-core,metadata-protocol,objectql,plugin-security): the sys_metadata family goes tenant-less; the per-organization overlay axis retires; managed content is sealed (ADR-0131 D6/D7/D13) #15206 and feat(objectql,cli): inventory + migration — four fates per object, mirrors deleted only after the id→name rewrite is verified, per-table boot report (ADR-0131 D10) #15211. This card closes completed in this act.

   ---

   Generated by Claude Code
3. objectstack-fleet

   removed

   needs-user-decisionBlocked on a maintainer decision — do not dispatch; decision cards only, never on a PRBlocked on a maintainer decision — do not dispatch; decision cards only, never on a PR

   on Oct 6, 2026
4. objectstack-fleet

   closed this as completedon Oct 6, 2026