Noticed by the os-dev seat while implementing #15435 (documenting the bulkActions and
datasets translation groups). Not fixed there on purpose — that card is ruled docs-only
on content/docs/ui/translations.mdx and explicitly fenced out of packages/. Filing rather
than dropping it.
The reading
packages/spec/liveness/translation.json's _note header states:
11 of 12 groups live; the twelfth, datasets, was seeded LIVE and DRILLED by #14253 with
its reader (translateDataset) in the same change, and flows is the one that is planned.
Measured on main at ef60224fc, straight off the ledger's own props map:
props: 14
live: 13
planned: flows
The 14 are name, label, locale, objects, apps, messages, globalActions,
dashboards, datasets, pages, flows, settings, metadataForms, settingsCommon.
The first three are the item's own identity fields, not bundle groups. Taking "group" to
mean the remaining eleven — which is the reading the header's own contrast with flows
implies — the count is 10 of 11 live, not 11 of 12. Either way the header's pair of
numbers does not match the file underneath it: there is no reading of props on which
twelve groups exist and eleven of them are live.
Why it is worth a card rather than a shrug
This is the header of the file whose entire job is to record what is live, and its own
correction history makes the point better than I can — the same sentence already carries a
warning about a previous version that described a group removed in 17.0.0, i.e. "prose
outliving its subject in the header of the very file whose rows warn about that." The
2026-09-02 pass (#14253) that corrected that clause is the same pass that moved the counts,
so the likeliest story is that adding the datasets row incremented both numbers when the
group-versus-identity boundary needed re-deriving instead.
No gate is red and no row is wrong — the per-prop status fields are all accurate, and
datasets really is live. Only the header's summary count is off, so this is an observation,
not a defect an author can trip over. Grading it low deliberately.
Suggested surface
packages/spec/liveness/translation.json — the _note header only. Worth deciding at the
same time whether the count should be prose at all, given #7377 retired the same class of
hand-maintained count elsewhere in this ledger family; a sentence that names the boundary
("every group but flows is live") cannot drift the way a pair of integers does.
Nothing in content/docs/ is implicated. #15435 is not addressed by this card, and this
card is not a blocker for it.
Generated by Claude Code
Noticed by the
os-devseat while implementing #15435 (documenting thebulkActionsanddatasetstranslation groups). Not fixed there on purpose — that card is ruled docs-onlyon
content/docs/ui/translations.mdxand explicitly fenced out ofpackages/. Filing ratherthan dropping it.
The reading
packages/spec/liveness/translation.json's_noteheader states:Measured on
mainatef60224fc, straight off the ledger's ownpropsmap:The 14 are
name,label,locale,objects,apps,messages,globalActions,dashboards,datasets,pages,flows,settings,metadataForms,settingsCommon.The first three are the item's own identity fields, not bundle groups. Taking "group" to
mean the remaining eleven — which is the reading the header's own contrast with
flowsimplies — the count is 10 of 11 live, not 11 of 12. Either way the header's pair of
numbers does not match the file underneath it: there is no reading of
propson whichtwelve groups exist and eleven of them are live.
Why it is worth a card rather than a shrug
This is the header of the file whose entire job is to record what is live, and its own
correction history makes the point better than I can — the same sentence already carries a
warning about a previous version that described a group removed in 17.0.0, i.e. "prose
outliving its subject in the header of the very file whose rows warn about that." The
2026-09-02 pass (#14253) that corrected that clause is the same pass that moved the counts,
so the likeliest story is that adding the
datasetsrow incremented both numbers when thegroup-versus-identity boundary needed re-deriving instead.
No gate is red and no row is wrong — the per-prop
statusfields are all accurate, anddatasetsreally is live. Only the header's summary count is off, so this is an observation,not a defect an author can trip over. Grading it low deliberately.
Suggested surface
packages/spec/liveness/translation.json— the_noteheader only. Worth deciding at thesame time whether the count should be prose at all, given #7377 retired the same class of
hand-maintained count elsewhere in this ledger family; a sentence that names the boundary
("every group but
flowsis live") cannot drift the way a pair of integers does.Nothing in
content/docs/is implicated. #15435 is not addressed by this card, and thiscard is not a blocker for it.
Generated by Claude Code