Retire "Console" as the name of the end-user surface; keep a name only for the admin surface (Setup)

[os-zhuang]

Blocked-by: #78

The decision

Maintainer decision, 2026-08-18. Scope, in their words: 「对于 console 我只要改 文档和 UI 文案」 — docs and UI copy only, the /_console URL is not touched. Naming, chosen from four options: 主界面不命名 + 管理面叫 Setup.

Concretely:

• The end-user surface gets no name. A reader opens ObjectOS, or your app — not "the Console". use/records describes opening a record in ObjectOS, not in the Console.
• The admin surface keeps a name: Setup. That word already appears on 18 English pages, so this is mostly a matter of using it consistently rather than introducing it.

Why, so the next person does not undo it

"Console" is an operator's word — server console, admin console — and it currently covers the entire runtime UI: end users working records, views, forms and approvals; admins configuring permissions and data sources; the AI Builder; the marketplace; the Account UI. One word addressing both a business user and an administrator makes the product sound like a control panel bolted onto something else.

Large products tend not to name their main surface at all — you open Notion, not "the Notion console". The split this repository's own information architecture already makes — use/ for end users, configure/ for admins — is the split the vocabulary should make too.

Scope in this repository

English sources under content/docs/. Every occurrence needs a judgement, not a search-and-replace, because the same word is doing three different jobs:

1. End-user context (use/**, most of build/**) — drop the noun. "In the Console, open the record" → "Open the record". Watch for sentences that become ungrammatical or lose their subject when the noun is removed.
2. Admin context (configure/**, parts of operate/**) — becomes Setup where it names the admin surface.
3. Not the product noun at all — /_console paths, CLI output samples, packages/console, Console UI in an architecture diagram describing the served bundle. ⛔ These stay. The URL is explicitly out of scope, so any code block, curl example or path reference keeps _console exactly as it is.

Category 3 is the trap: a global replace will corrupt URLs and code samples that must not change, and those are the occurrences a reader copies and runs.

docs/TRANSLATION.md also lists Console in the never-translate glossary. Update the glossary in the same PR — for the surviving Setup, and drop the retired term rather than leaving a rule for a word that no longer appears.

Not in this repository — do not attempt from this card

The UI copy half lives elsewhere and is not dispatchable from here:

• objectui — a case-sensitive grep for Console hits 179 files, but that count mixes the product noun with component names, type names and identifiers. Someone has to separate user-visible copy from code identifiers before that work can be sized; the number above is not a work estimate.
• objectstack — packages/cli/src/utils/format.ts:579 prints ➜ Console: on startup, which is the first place a new user meets the word.

Both need their own cards in their own repositories, routed by triage. Filing them is not this card's job and dispatching into those lanes is not this seat's to do.

Ordering

Serial with #78, not parallel. #78 (the 17.0 alignment) touches quickstart, faq, build/data/index, reference/field-types, configure/permissions/** and more; "Console" appears across essentially the whole corpus, so the two file surfaces overlap almost completely. Correctness first: a reader currently following quickstart.mdx on Node 20 fails, which outranks a naming improvement. The rename is also easier to apply to a corrected corpus than the reverse.

[os-support-ai]

Triage: promoted to pm:queue. The decision is already made and recorded in the body (maintainer, 2026-08-18: docs + UI copy only, /_console URL untouched; end-user surface unnamed, admin surface = Setup), so this is an execution card, not an inbox card.

The body's Blocked-by: objectstack-ai/objectos#78 is discharged: #78 closed 2026-08-18 12:36Z via merged PR #82 (the 17.0 alignment). The serial-ordering reason (near-total file overlap with the corrected corpus) is now satisfied in the right order — the rename applies on top of the corrected pages.

Bundle note: #89 (glossary double-Console + duplicate /_console/ in Surface) rides with this card — same claimant, same PR or back-to-back, per #89's own analysis that a mechanical rename would produce "Setup … Distinct from Setup" and miss the URL defect. The authoritative URL for each surface must come from the runtime's routing, not from either glossary sentence.

Also per the card's own scope: the objectui / objectstack UI-copy halves are separate cards in their own repos — filing them goes through triage when this card's docs half lands and the vocabulary is proven out.

Execution lane: domain:devx seat (objectos execution folds into devx; no repo:objectos seat by the 2026-08-18 Option B ruling).

---

Generated by Claude Code

[os-zhuang]

Measured before dispatch — and the card's framing has a gap

Counted on 6fca5d1, English pages only:

160 occurrences of Console across 45 of 79 pages. Nine are inside code fences. The rest is prose needing a per-occurrence call.

Section	Occurrences	Pages
build/	57	15
configure/	25	8
resources/	23	4
root pages (index, why, quickstart, architecture, extend-existing-systems)	24	5
reference/	15	5
use/	6	5
operate/	5	3
deploy/	0	0

The gap

I wrote this card around two contexts — end-user (drop the noun) and admin (becomes Setup) — with the implicit assumption that the bulk sat in use/. It does not. use/ holds 6 occurrences; build/ holds 57, nine times as many, and the card says nothing about what a build/ context becomes.

The maintainer's decision does extend there coherently — if the main surface has no name, then a builder creating an object is doing it "in ObjectOS", the same as an end user opening a record. But build/ also carries occurrences that are architectural statements about the UI layer rather than instructions to a person: "Console views", "the Console's generic action runtime", "install apps via the Console marketplace". Those are closer to category 3 (not the product noun as a place the reader goes) than to either rewrite.

So the three categories stand, but the weight is in the hardest place, and whoever executes this should expect build/ to be most of the work and most of the judgement.

⛔ If an occurrence fits none of the three categories, stop and report rather than inventing a fourth. A rename that grows a category mid-sweep produces exactly the inconsistency this card exists to remove.

Sizing

This is larger than #78 (19 files) by a factor of two-plus in pages touched. If it exceeds one reviewable PR, land the coherent half — configure/** → Setup, which is the least ambiguous slice — as Part of #79, file the remainder, and say so. ⛔ Do not land a partial rename that leaves two spellings of the same surface in the corpus at once; split along a boundary a reader would not notice, not through the middle of one.

Prerequisites, both in resources/glossary.mdx

• glossary.mdx defines Console twice, and each entry says it is "Distinct from Console" #89 — the Console entry is defined twice, each saying it is "Distinct from Console", both giving the same /_console/ URL. A mechanical rename produces "Setup … Distinct from Setup". This card owns fixing that; glossary.mdx defines Console twice, and each entry says it is "Distinct from Console" #89 is its record.
• actions.mdx built-in share action names role as a recipient kind — same retired vocabulary as #80 #91 — records that record-access.mdx:15 names three of five recipient kinds while line 66 of the same page names all five. Unrelated to the rename, but it is in a file this sweep may touch; leave it alone and let actions.mdx built-in share action names role as a recipient kind — same retired vocabulary as #80 #91 carry it.

---

Generated by Claude Code