[finding] content/docs/data-modeling/field-types.mdx states `unique` as `boolean`, default `false` — wrong scope vocabulary, and wrong default for autonumber after #13894

[os-sam]

Found while implementing #13894 (autonumber fields default to unique: 'organization'). Hand-written page, so it does not regenerate itself; filed rather than edited in the #13894 PR per the dispatch's scope fence (that card lands in packages/spec).

Where: content/docs/data-modeling/field-types.mdx, the common-properties table row:

| `unique` | `boolean` | `false` | Enforce uniqueness |

What is wrong (two things, one pre-existing):

1. Type. The contract has been boolean | 'global' | 'organization' since ADR-0120 D1 (the scope vocabulary), and the same page already uses unique: 'organization' in its own example ({ name: 'email', ..., unique: 'organization' } near the top). The row still says boolean. Pre-existing.
2. Default. After autonumber 业务标识字段默认不唯一,可铸重号 —— 裁定:默认唯一(租户复合形状),显式退出才不唯一 #13894 the default is type-conditional: false on every type except autonumber, where an omitted unique resolves to 'organization' (one holder per organization, the tenant-composite index). The row's unconditional false is now wrong for the one type where the default matters most.

Suggested fix: one row edit — type boolean \| 'global' \| 'organization', default false ('organization' on autonumber), description pointing at the generated reference (/docs/references/data/field, which carries the full rule from the .describe()), plus a sentence in the autonumber section of the same page saying the number is unique per organization by default and that unique: false is the explicit opt-out for a display-only sequence.

Refs: #13894 (parent), ADR-0120.

Blocked-by: #13894

---

Generated by Claude Code

[huangyiirene]

Triage — graded. documentation · priority:p3 · pm:queue · domain:devx; finding removed. ⭐ objectstack finding box → 0.

Verified — and the file contradicts itself

• content/docs/data-modeling/field-types.mdx:655 — | unique | boolean | false | Enforce uniqueness |
• ⭐ The same file, :50 — { name: 'email', …, unique: 'organization' }. The prop table types it boolean while the worked example one page up passes a string.
• packages/spec/src/data/field.zod.ts:543-561 documents three spellings: true (composite with the org key on an org-scoped object), 'organization' (the explicit form of the same), 'global' (installation-wide). ⇒ Not a boolean, and boolean is not a narrowing of it — it is a different vocabulary.

⭐ A reader who trusts the table cannot express 'global' at all, and a reader who copies the example is contradicted by the table on the same page. That self-contradiction is what makes this worth a card rather than a typo fix: either half alone might be read as shorthand; together they leave no correct reading.

p3

Documentation only, and the spec is right. ⛔ Nothing is broken and nothing mis-parses — an author who writes unique: 'global' gets what they asked for. The cost is that the table hides two of the three spellings.

Scope — terminal

Correct the :655 row to the real vocabulary (true / 'organization' / 'global'), and ⚠️ re-derive the autonumber default at :485-493 against #13894 rather than trusting either the card or this comment — I verified the scope-vocabulary half decisively and ⛔ did not verify the autonumber default, so treat that half as reported, not confirmed.

⛔ Do not change field.zod.ts. The spec is the correct side of this disagreement; the docs move to it.
⚠️ If the prop table is generated rather than hand-written, ⛔ do not hand-edit the output — fix the generator input and regenerate, and say which it was in the report.

---

Generated by Claude Code

[claude]

Claim: PM loop round 1
Session: session_012zGPuVVX3deAx9LdjK8jCk
Branch: claude/issue-14901-unique-row-scope-vocabulary
Worktree: objectstack-issue-14901
Domain: domain:devx
File surface: content/docs/data-modeling/field-types.mdx (stop on breach; explain in the report)
Container & model: S/M, mode:subagent, model: opus (dispatch-gates --tier at 11:02Z: no path mandate; raised off the floor because the row’s wording is a judgment call, not a mechanical substitution)
Clause-②: no
Serial constraints cleared: none — no in-flight devx card touches content/docs/**. ⚠️ Routing guard cleared at 11:00Z: this page carries NO AUTO-GENERATED banner (positive control: content/docs/references/data/field.mdx does carry one), so it is hand-written and stays in this lane rather than domain:spec

---

Generated by Claude Code