Vocabulary pass, layer 2 + Dataset & Releases (DISCUSSION FIRST — do not implement)

[JArmandoAnaya]

Motivation

Layer 1 of the vocabulary pass (#292) was mechanical work: raw kernel identifiers were replaced by existing or obvious labels, and the Versions tab was renamed. What remains is not mechanical. It renames concepts — promote, partition, trunk, manifest — whose current words are the kernel's own, it redesigns an error surface, and it merges two navigation destinations. Each of those needs a decision before any code is written, so this issue exists for tracking and discussion only.

Do not implement from this issue. Every item below needs a founder decision first.

Open questions

1. Promote, partition, trunk and manifest as user-facing copy. These words appear in user-facing prose in BatchesScreen, ApproveDialog and DatasetScreen, and they are simultaneously the kernel's exact vocabulary. The same-sentence rule — a refusal and the screen describing it share their wording — is load-bearing here. Renaming them for users means either a translation layer that must never drift, or accepting the kernel's words as the product's words. Which of the two?

2. Error codes used as headings. patterns/AsyncStates.tsx:116 renders the machine-readable code as the error heading, so a user sees a title reading "SCHEMA_NOT_FOUND". This is a design decision rather than a bug: the code is what a bug report should quote and what a client branches on. If it changes, the redesign has to keep the code visible somewhere a reader can copy it from.

3. Renaming the Dataset destination to "Dataset & Releases". (Premise updated 2026-08-05: this question originally read as a merge between the "Versions" tab and the Dataset screen. The IA restructure (IA restructure: Dataset is a tab, Schema history nests, Overview is a dashboard #310) removed the Versions tab — schema history now nests inside the Schema tab, ?tab=versions redirects there, and the information-architecture skill states the ledger/reader division. The split is therefore no longer Versions against Dataset.) What remains is the split between the Schema tab and the Dataset tab: schema versioning lives entirely inside Schema, while releases — the thing a version is eventually exported as — live under Dataset. The narrowed question is whether the Dataset destination is renamed "Dataset & Releases" to say so, now that nothing about schema versions competes for the name. Renaming touches roughly six test files (dataset.test.tsx, navigation.test.tsx, shell.spec.ts, navigation.spec.ts, plus the route and parent-label sites) and the left rail's pinned two-link contract at shell.spec.ts:157.

4. Inline schema creation from the approve dialog, deferred out of the work that humanized SCHEMA_NOT_FOUND in that dialog (Humanize SCHEMA_NOT_FOUND in the approve dialog #291). Should the dialog offer creating version 1 in place, or is the link out to the schema tab the right scope forever?

Exit criteria

A decision comment per question, then implementation issues filed for whatever survives.

[JArmandoAnaya]

Q3's premise updated, and the milestone removed, following the 2026-08-05 backlog audit.

Q3 was written against a world that still had a "Versions" tab in it. The IA restructure (#310, landed as 92337cf) removed that tab: schema history now nests below the Schema editor, ?tab=versions redirects through resolveProjectTab, and the information-architecture skill states the ledger/reader division outright. Q3 has been rewritten to the split that actually remains — Schema tab against Dataset tab — and narrowed to the rename alone. Its stale citation is corrected in the same edit: the rail's two-link assertion sits at shell.spec.ts:157, not :153.

Q1, Q2 and Q4 were re-verified at HEAD 47dc1f0 and are accurate as written. The kernel's vocabulary is still in user-facing prose, AsyncStates.tsx:116-118 still renders code as the heading, and the approve dialog still links out to the schema tab through approve-go-schema rather than creating version 1 in place. All three are untouched.

The milestone has been removed and Journey navigation closed. This was the last open issue in that milestone, and the issue is discussion-only by its own first line — holding a milestone open on a ticket that must not be implemented from measures nothing.

[JArmandoAnaya]

Milestoned 0.1.0 per the default rule (Armando, 2026-08-07): everything lands in 0.1.0 unless explicitly moved.

The DISCUSSION FIRST banner in the title still governs — milestone membership does not make this issue implementable.