LearnNewsExamplesServices
Frontmatter
id17264
titleUnify the cockpit status-chip family under one designed system
stateClosed
labels
enhancementai
assigneesneo-fable-clio
createdAtAug 17, 2026, 12:26 AM
updatedAtAug 21, 2026, 1:27 PM
githubUrlhttps://github.com/neomjs/neo/issues/17264
authorneo-fable-clio
commentsCount0
parentIssue14560
subIssues[]
subIssuesCompleted0
subIssuesTotal0
contentTrust
projected
quarantined0
signals[]
blockedBy[]
blocking[]
closedAtAug 21, 2026, 1:27 PM
milestonev13.2

Unify the cockpit status-chip family under one designed system

Closed Backlog/active-chunk-16 enhancementai
neo-fable-clio
neo-fable-clio commented on Aug 17, 2026, 12:26 AM

Unify the cockpit status-chip family under one designed system

Context

The §04 implementation sub for the chip ladder (spec: #17263 — spec-first, this ticket starts only after that spec passes review). The cockpit grew five status idioms independently: the per-agent telltale (telltale.mjs), the spine banner (spineBanner.mjs + skin), the viewer-wake telltale (viewerWakeTelltale.mjs + skin, landed 2026-08-16), the event-kind chips (EventChip.mjs/kind registry), and the state dots (StateDot.mjs). Their honesty semantics are deliberately consistent (absence ≠ unknown, exception-only card pixels, reasons verbatim); their VISUALS are five ad-hoc dialects — different anatomies, paddings, mark treatments, token indirections.

The Problem

A cockpit whose status vocabulary looks like five different apps reads as unfinished regardless of how honest each surface is — this is a load-bearing slice of the operator's "a lot of love missing" verdict. The duplication is also maintenance debt: each new surface re-invents anatomy (the viewer-wake telltale copied the spine banner's token-indirection idiom by hand this week — the copy worked, and it is still a copy).

The Fix

Implement #17263's chip-family ladder: one shared anatomy (mark + text + optional detail affordance) expressed as a small set of SCSS building blocks (shared placemat classes or mixins in the fleet skin layer, token-only), then migrate the five idioms onto it per the spec's migration notes. Rendering derivations (describe* functions) stay untouched — this is a skin-layer unification; the semantics modules keep owning WHAT to say, the family owns HOW it looks.

Acceptance Criteria

  • The shared chip-family SCSS primitives exist (token-only, both-theme via --fm-*), and all five idioms consume them — zero per-idiom anatomy re-declaration for the shared parts.
  • Visual states carry the spec's mark+ink mapping; non-hue-alone and reduced-motion laws hold (existing spec pins keep passing).
  • The check-theme-surfaces guard stays green (incl. shell-seam check 5); no drawer-pane root regains frame ownership.
  • #14618's visual-regression baseline captures the unified family as its reference set (or, if #14618 lands later, this ticket leaves the capture list ready in its PR body).

Out of Scope

The spec itself (#17263) · new status surfaces · behavioral/derivation changes · the dashboard theme layer (#17242).

Related

Epic #14560 (parent) · #17263 (the spec this implements) · #17242 (theme foundation) · #14618 (evidence instrument) · sibling pass: typography/density (see the §04 sibling sub).

Live latest-open sweep: latest 20 open checked 2026-08-16T22:22Z, no equivalent; A2A herd-window sweep clean.

Origin Session ID: 71baabc5-3ebe-46ff-99ce-a301e78cb7c5

Retrieval Hint: query_raw_memories("cockpit status chip family unification telltale banner state dot one designed system")

tobiu referenced in commit 04b47ce - "feat(fleet): unify the status-chip family on the token geometry contract (#17264) (#17455) on Aug 21, 2026, 1:27 PM
tobiu closed this issue on Aug 21, 2026, 1:27 PM