docs(adr): ADR-0131 — organization ownership is total: no NULL organization_id; declared metadata stays in code; rows only when an organization authored them (Refs #13564)

[hotlong]

Summary

Adds ADR-0131 (Proposed); marks ADR-0126 Superseded; annotates ADR-0105 D10 (withdrawn) and ADR-0005 (per-organization overlay axis retired for now). Staging (D14): one pre-17.3 revert of the unreleased ADR-0126 flow machinery (C0); everything else is the v18 line. Three sentences:

1. Metadata is the registry, in two provenances. A managed package is code: edited in code only, changed by publishing a new version, never materialized as rows, and sealed at runtime (no overlay, no disable, no clone — packaged flows included). Metadata authored at runtime — Studio, the cloud build agent, or a template package copied once into the database — is saved in the database and edited in the UI; it is the environment's, and its ledger carries no organization column. Template packages are refused on shared-DB multi-tenant deployments.
2. A row with an organization column exists only when an organization authored it — assignments (this user holds this position or set), business units, sharing rules, business data — NOT NULL, referencing registry items by name. The catalog itself (positions, permission sets, capabilities) has one home, the environment registry: single-tenant admins author it there (the organization is the environment); shared-DB tenants assign but do not define. The four catalog tables retire (ADR-0094 completed).
3. A table with no organization column is deployment-level or code-level, governed by permission, not by a wall.

Consequences: NULL has nothing left to mean (D1); one predicate for Layer 0 and every driver (D8); a missing stamp is a refused write (D9); seeders, per-organization catalog machinery and the #13491 ledger retire (D13); sys_metadata loses its column with no split because no per-organization metadata remains (D6); #13636 / PR #14923 superseded (§1.6); no platform organization (§1.5, rejected alternative).

Maintainer rulings, verbatim in the record's header — among them 「数据库中不应该有允许 org_id 为空的状况」「既然不让改，又要求每个租户 seed 一遍，好像很蠢」「我宁可先不让他编辑」「创业阶段，应该定一套最稳定可靠的方案」「代码推送过来的元数据就只能在代码中修改…studio 界面上配置的元数据…可以在界面上修改」「先完全封死。flow 也先不让改…模版形式直接进库…单库多租户禁止安装…受管软件包…不让改」.

What this PR is and is not

• Docs-only. One ADR, three amendment notes, one empty changeset ("Releases nothing").
• ⛔ Governed surface (docs/adr/**) — human merge only, no auto-merge armed (Prime Directive feat: Comprehensive CRM example demonstrating all ObjectStack protocol features #14).
• ⛔ No implementation card is filed before this merges (ADR-0130 precedent). The twelve-card plan is §8. The unreleased ADR-0126 flow disable/clone machinery (L3: runtime consult at the execute() seam + trigger unbind + retire the #10243 flowEnabled map (ADR-0126 §7.2) #12158, L4: flow clone action — whole-definition copy, mandatory new name, no ancestry (ADR-0126 §7.1) #12156, Ledger convergence: registration home + one store implementation (ADR-0126 §4/§8, maintainer-ruled) #12419 — landed after the 17.2.0 tag) is removed before the next release (D6).
• check:adr-links and check:adr-anchors pass locally.

Open questions for the merge decision (§6)

Four of five were accepted as proposed on 2026-09-04 (「接受你的建议」) and folded into D5/D6/D7. One remains:

1. Existing customized template rows: keep as Default Organization overrides, or accept loss under the startup posture? Ruled when C4 is cut.

Post-17.2 audit verdicts are recorded in §7; revert cards #15024 (ADR-0126 machinery) and the #14949 NULL-screen revert are filed for landing before 17.3; PR #14923 closed unmerged; ADR-0126 marked Superseded in PR #15023.

Refs #13564 · #13636 · #10103 · #13491 · #2734 · #12699 · #11665 · #12150 · #14484 · #14547 · cloud#1239 · cloud#1664

🤖 Generated with Claude Code