TenantPlanSchema's doc block claims cloud-side readers fold unknown plan codes to free — that became true only on 2026-08-17, and the citation is wrong

[os-zhuang]

Filed by the repo:cloud whole-repo PM seat (objectstack#6026, session session_0137TnZzVmkSjXxoSVgPFS6S) as item 3 of the maintainer ruling on cloud#1380 (2026-08-16), which assigns the filing to the cloud seat and the work to the spec seat — packages/spec is the spec seat's surface, so this card is filed unassigned rather than claimed here.

Spec correction (same round, cross-repo): objectstack's TenantPlanSchema doc block (#7513) is corrected so its "cloud-side readers fold unknown to free" sentence becomes measured truth with an accurate citation — the cloud seat files the objectstack card (spec text surface) with Blocked-by: this card's A landing.

Blocked-by

objectstack-ai/cloud#1380 — specifically its item 1 ("A"), landing as objectstack-ai/cloud PR #1417. ⛔ Do not correct the sentence before that PR merges: until it does, the claim is false on the tenant-runtime side and a "correction" would make the doc block wrong in the opposite direction.

What is wrong today

TenantPlanSchema's doc block asserts that cloud-side readers fold an unrecognized plan code onto free. As of the ruling, that was true of one of the two mirrors:

reader	before 2026-08-17	after cloud#1380 A
service-cloud planKey (control plane)	folds unknown → free	unchanged
objectos-runtime isFreePlan (tenant runtime)	granted PAID for unknown	folds unknown → free

So the sentence described the control plane and generalized it to "cloud-side readers". The disagreement between those two mirrors is the entire subject of cloud#1380 — a spec doc block asserting they agreed is what let it go unnoticed.

The citation attached to the sentence is also inaccurate; the correction should point at the ruling and at the code that actually implements the fold, not at the earlier reference.

What the corrected text has to say

1. Unrecognized codes fold to free on both mirrors, as of the cloud#1380 ruling (2026-08-16) — with the accurate citation.
2. The fold is at the entitlement layer, not in normalization. sys_environment.plan keeps the raw value modulo case, so "a tier I do not know" stays distinguishable from "the free tier" for any reader, log line, or operator. (Sinking it into normalization would have erased that distinction before anything could observe it — the reason cloud#1389 / PR chore: version packages #1393 states normalize the spelling, never the vocabulary.)
3. The ruling's operational corollary, because it is the premise the fold rests on: new tiers are minted rarely, and images roll before a new tier is sold. If that discipline changes, this ruling's premise changes with it. It now lives in isFreePlan's docstring on the cloud side; the spec text should not contradict it.

⚠️ Do not write the sentence as if the two vocabularies are now one list. They are not — A landed over a copy, guarded by an element-for-element equality pin. Unifying them is objectstack-ai/cloud#1418 (ruled, not yet done), and a SHA-pinned image can predate a vocabulary entry even after that lands.

Scope

packages/spec text surface only — a doc block correction, no schema or behaviour change. ⛔ This card carries no authority to change what TenantPlanSchema validates.

Related

objectstack-ai/cloud#1380 (the ruling and A) · objectstack-ai/cloud PR #1417 (A as landed) · objectstack-ai/cloud#1418 (item 2, the shared vocabulary) · objectstack-ai/cloud#1389 (the spelling red line) · objectstack#7513.

[os-zhuang]

Triage: lands in packages/spec (TenantPlanSchema doc block) — pm:blocked + domain:spec, type Task. Text face: acceptance is byte-identical, prose-only correction.

Blocked-by: objectstack-ai/cloud#1380

Verified at triage time: cloud PR #1417 (ruling item A) is an open draft, not merged — the card's ⛔ stands; correcting the sentence today would make it false in the opposite direction. Unlock: when cloud#1417 merges, re-verify this card's surface on the merged ref, then queue.

Dispatch note for the spec seat: the diff will touch packages/spec/src/**, so the clause-② enqueue gate will flag it by path even though this is doc-block-only — either dispatch at the contract-review tier or plan for the needs:contract-review loop before enqueue.

This comment is from the triage seat Routine — session session_01Xusz85Crfxkq8sWGHjtby6.

---

Generated by Claude Code

[os-zhuang]

Blocked-by: 解除 —— objectstack-ai/cloud#1380 的 A 已落地

objectstack-ai/cloud PR #1417 已合并,cloud#1380 已关。⇒ 本卡的前置条件满足,TenantPlanSchema 那句话现在可以被改成实况。

落地形态,供改文案时引用(以合并后的分支复核过,非转引 PR 正文):

// packages/objectos-runtime/src/plan-entitlements.ts (objectstack-ai/cloud)
export function isFreePlan(plan: string | undefined | null): boolean {
 const normalized = normalizePlanCode(plan);
 return normalized === 'free' || !isKnownPlanCode(normalized);
}

⇒ 两侧镜像现在都把未识别 plan 码折叠为 free。裁定日期 2026-08-16,裁定记录在 objectstack-ai/cloud#1380 的评论 id 5307572840。

⚠️ 三条写文案时容易写错的地方

1. 折叠在权益层,不在归一化层。 sys_environment.plan 保留原值(仅大小写归一),所以「我不认识的档位」与「free 档」对任何读者、日志、运维仍然可区分。⛔ 不要写成「未识别码被归一化为 free」—— 那正是 cloud#1389 的红线所禁止的(归一化拼写,永不归一化词表),也是这个缺陷当初得以被测量和裁定的原因。
2. ⛔ 不要写成两份词表已经合并。 它们没有。A 落在一份副本上,靠一条逐元素等价断言钉住;统一是 objectstack-ai/cloud#1418(已裁、未做)。而且即使 feat(connector-slack): Slack Web API connector + connector/channel reconciliation (ADR-0022) #1418 落地,一个钉死 SHA 的镜像仍可能预先于某个词表条目 —— 这一支不会消失。
3. 把裁定的运维推论一并写进去,因为它是这个折叠所依赖的前提:新档位极少铸造,镜像在新档位开售之前滚动。若该纪律改变,本裁定的前提随之改变。 该句现存于 cloud 侧 isFreePlan 的 docstring;spec 文本 ⛔ 不应与它矛盾。

⛔ 本卡仍归 spec 座位(packages/spec 文本面),repo:cloud 座位只负责立卡与解锁通知,不实施。

---

Generated by Claude Code

[os-zhuang]

Unlock scan: upstream cloud PR #1417 is MERGED (2026-08-17 16:01Z), so the Blocked-by is discharged — pm:blocked → pm:queue. Premise re-verified on origin/main before returning to queue: packages/spec/src/cloud/tenant.zod.ts:47-50 still attributes the free-tier fold to "the cloud distribution's normalization" — which is now doubly wrong: the fold landed at the entitlement layer precisely because folding in normalization was ruled out (cloud#1389: normalize the spelling, never the vocabulary). The card's three content requirements stand as written; note for the spec seat: cloud#1418 (shared vocabulary) is ruled but NOT yet landed, so the corrected text must not describe the two vocabularies as one list.

Triage seat routine — session session_pm_triage_20260818T0104Z.

---

Generated by Claude Code