prove an open-only install can RAISE the wall — the matrices exist but every one of them stubs the posture

[hotlong]

Blocked-by: #16130

The acceptance half of #16130. That card moves the org-scoping registrar into the open core; this one proves an open-only install can actually raise the wall. ⛔ #16130's PR must not claim the acceptance criterion is met — it is discharged here.

The precise gap, measured

The open tree already has the matrix. packages/rest/src/single-kernel-isolated-api-key-matrix.test.ts and single-kernel-isolated-session-org-claim-matrix.test.ts — the two suites the cross-organization repairs pinned (#15256, #15409) — drive a live isolated posture at REST level and assert the whole thing: an ex-member's API key and session refused, a member reading only its own organization, an organization-less caller refused, and the phantom controls that prove the per-type gate is doing the work.

⚠️ What they do not do is produce the posture. Both raise it with a hand-written stub:

const tenancyServiceProvider = async () => ({ posture: 'isolated' });

⇒ Today the open tree proves the wall behaves correctly given a posture, and proves nothing about whether anything open can produce one. Before #16130 that was unavoidable — the only registrar was cloud-private. After it, it is a gap nobody would notice, because every existing suite goes on passing against its stub.

Scope

An open acceptance that raises the posture through the real open org-scoping registrar — the plugin #16130 lands — rather than a stub, and runs the matrix against it.

⛔ Not a port of cloud's ee-tenant-crm-showcase / ee-group-showcase suites, and ⛔ not a new walled showcase app. Those were considered and are out of scope: the matrix exists, and duplicating it is how two copies drift.

⭐ The assertion that makes this card worth having, and it must fail before #16130 lands: with the open plugin mounted and no stub, getService('org-scoping') resolves and the effective posture reads isolated. On today's tree that is unsatisfiable — which is the point.

Acceptance

1. An open-only composition mounts the open org-scoping plugin and boots with the wall ACTIVE — asserted from the resolved posture, ⛔ not from a stub's return value.
2. The existing matrix runs against it unchanged in substance: ex-member API key refused; ex-member session refused; a member reads only its own organization; an organization-less caller refused; a healthy member still reads and writes (⛔ without this control the refusals prove nothing).
3. ⛔ No licence check is reachable from the open composition — a deployment that mounts only open packages gets a working wall. That is the whole claim of Bring single-database multi-organization isolation back to the open core — the wall is already open, only the org-scoping switch is closed (~1350 of 1660 lines move; the licence gate stays) #16130 and this is where it is measured.
4. The stub-based suites stay as they are. They pin the wall's behaviour given a posture, which remains a distinct question from whether one can be produced; ⛔ do not delete or rewrite them to point at the plugin.

Refs: #16130 (the move) · #15256 / #15409 (the matrices and what they pin) · cloud packages/organizations · ADR-0105 D1 (the posture is the authoritative knob).

[hotlong]

Acceptance sharpened by the maintainer's statement of the goal, and by one more measurement.

Maintainer, 2026-09-06, verbatim: 「迁移之后的效果应该是开源版就可以把元数据应用使用单库多租户的方式运行。」 ⇒ the bar is a running open-source multi-tenant install, not a registrable service.

⭐ The missing measurement, which makes acceptance criterion 1 sharper than it was written: today an open-source install that sets OS_TENANCY_POSTURE=isolated cannot enforce it — its only route is OS_ALLOW_DEGRADED_TENANCY=1, i.e. the wall configured but not enforced. That is exactly the shape three cross-organization defects were closed against this week, and the one ADR-0131 D9 refuses.

⇒ Criterion 1 is restated as: an open-only composition with OS_TENANCY_POSTURE=isolated and OS_ALLOW_DEGRADED_TENANCY UNSET boots with the wall ACTIVE, and the matrix passes against it. ⛔ Setting the degrade flag anywhere in this acceptance voids it — the flag is the thing this card exists to make unnecessary.

⚠️ State the negative control too: the same composition without the open org-scoping plugin must still refuse-or-degrade exactly as today. If it silently gains a wall from somewhere else, the acceptance is measuring the wrong thing.

Everything else on this card stands.

[os-trump]

解锁 —— 本卡等的代码已在 origin/main 上,而它等的卡永远不会先于它关闭

pm:blocked → pm:queue,domain:services PM 席 · session session_012zTkyNHJ7TkuN2oXtP5x37(os-trump)· R25。标签已在另一次调用中读回为 ["priority:p1","security","pm:queue","domain:services"],assignee 空。

为什么这不是「阻塞项没关就放行」

正文的 Blocked-by: #16130 按字面仍成立(#16130 open)。但那个块在实质上已耗尽,而且它是环形的:

• Bring single-database multi-organization isolation back to the open core — the wall is already open, only the org-scoping switch is closed (~1350 of 1660 lines move; the licence gate stays) #16130 的开源半边(PR feat(organizations): bring the multi-organization runtime back to open core — the org-scoping registrar ships open, the licence gate stays in cloud (ADR-0132) #16215)已落地 —— 实测 git log origin/main --oneline | grep -c '(#16215)' = 1,阳性对照 '(#16585)' = 1、阴性对照 '(#99999999)' = 0(修正 26:没有反向对照的零不是证据);检出非 shallow(修正 89)。
• packages/plugins/organizations/package.json 在 origin/main 上(阴性对照:不可能的路径答空)。docs/adr/0132-*.md 同在。
• 而 Bring single-database multi-organization isolation back to the open core — the wall is already open, only the org-scoping switch is closed (~1350 of 1660 lines move; the licence gate stays) #16130 在 2026-09-07T02:26Z 自己列出的仓内剩余项就是本卡(另一项 cloud#2027 在另一个仓,且同样 pm:blocked 在 Bring single-database multi-organization isolation back to the open core — the wall is already open, only the org-scoping switch is closed (~1350 of 1660 lines move; the licence gate stays) #16130 后面)。

⇒ 本卡等 #16130,#16130 在本仓等本卡。按字面判据这一对永远不会解锁 —— 与 #13566 今天那条同族(修正 90:解除条件键在一个没有任何动作会满足的读数上)。⛔ 一个 p1 security 验收卡不该死在这上面。

⭐ 本卡自己的「必须失败」判据,现在已经翻面

正文写着:

with the open plugin mounted and no stub, getService('org-scoping') resolves and the effective posture reads isolated。On today's tree that is unsatisfiable — which is the point.

那句话写于 2026-09-06T02:57Z。现在它为假:插件在树上了。⇒ 本卡从「不可满足」变成「可做」,这正是它设计的开工信号。

⚠️ 但请派发时注意方向:那句原话是要求这条断言在 #16130 落地前失败。它现在应当通过;⛔ 它不再是一条会失败的断言,不要把它当回归测试的红灯来写。真正要守的红线是验收项 3 —— 开源组合里不可达任何 licence 检查。

⛔ 未派发

本轮维护者未指示开新一波,本席已有 3 个在飞 dev(#13566 / #15358 / #15991)。本卡入队待派,⛔ 不在本轮认领。

派发时给 dev 的既定读数,免得重推:验收项 1 的姿态必须从解析出来的 posture 断言,⛔ 不从 stub 的返回值;验收项 4 —— single-kernel-isolated-api-key-matrix.test.ts 与 single-kernel-isolated-session-org-claim-matrix.test.ts 两套 stub 套件原样保留,⛔ 不删不改指向插件(它们钉的是「给定 posture 时墙的行为」,与「能不能产生一个 posture」是两个问题)。

---

Generated by Claude Code