# One Technical-Light family Review date: November 12, 2026. Mode: Operate. This is a recommendation package and a set of proposed visual artifacts, not an implementation or a production acceptance report. ## Direction Keep the established visual identity: IBM Plex Sans, IBM Plex Mono for identifiers and measurements, warm paper, white working surfaces, fine neutral rules, compact rectangular status chips, a 220px desktop rail, and restrained product accents. Improve the system once, then apply it consistently. Do not give each project a new layout, font, card treatment, or status palette. The current source in `ZB.MOM.WW.Theme` is the visual authority. Its `Directory.Build.props:7` declares 0.5.3. Consumer versions differ; a version declared in a checkout is not evidence of what is deployed. The old `components/ui-theme/README.md` “not started” matrix and the shared-contract document's 0.2.0 description are historical evidence, not the present adoption state. ## Common contract | Element | Family rule | Allowed local variation | |---|---|---| | Shell | ThemeShell, one main landmark, a persistent current location, native mobile nav disclosure | Product name, role-aware route groups, optional pinned session footer | | Accent | Existing approved product accent; supply matching deep/hover/focus/tint tokens | Preserve Historian green, Overview purple, and any source-verified product accent; no per-page palette | | Typography | Plex Sans; 14–15px working text; 24–26px page heading in proposals; 18px section heading; mono only for data | Domain code/editor font and data density | | Surfaces | Paper `#f4f4f1`, card white, neutral border; existing 8px panel radius | Specialized topology/editor canvas | | Spacing | 4, 8, 12, 16, 24, 32px; close related controls, separate tasks | Dense desktop tables can use smaller row padding with adequate targets | | Page header | One h1, short scope/context, freshness where relevant, one primary action | Read-only surfaces need no primary action | | Actions | Shared primary, secondary, danger, ghost treatments; explicit busy/disabled/error states | Domain command names and policy rules | | Data | Labeled filters above data, scoped scrolling, real headers, sort state, stable identity | Tree/table/editor presentation appropriate to task | | Forms | Programmatic label, hint/error association, required state, field-local recovery | Protocol-specific editors remain local | | Status | One semantic palette plus plain state text; separate quality, role, transport, freshness | Domain vocabulary stays accurate: pooled ≠ in use, active ≠ leader, disabled ≠ failed | | Time | Explicit zone and timestamp semantics, relative age plus exact time where useful | UTC export, local operational display, or an explicit zone selector | | Dialogs | Accessible name, initial focus, modal isolation, Escape/cancel where safe, focus return | Domain-specific confirmation text and authorization | | Responsive | Rail collapses below 992px; content remains visible; details stack; wide grids scroll inside their container | A complex desktop editor may offer a clearly scoped mobile summary | | Touch | Aim for 44px touch actions; retain efficient desktop density | 24px minimum target/spacing rule must be assessed separately from the 44px design target | | Motion | Useful state feedback; no repeating entrance choreography; reduced-motion alternatives | No requirement to add motion to operational screens | All mockups share [one stylesheet](mockups/shared.css) and vendored Plex assets. Proposed darkened status inks are intentionally shown in every concept. They are candidates for new semantic foreground tokens, not instructions to repurpose every existing dot/chart token. Mockups simplify domain data to make the recommended hierarchy reviewable. New filters, detail panes, and state selectors are explicitly proposals; they are not claims about existing functionality. ## Shared findings and implementation recommendations ### DS-01 · P1 · Small status and supporting text need accessible foreground tokens **Evidence:** `ZB.MOM.WW.Theme/src/ZB.MOM.WW.Theme/wwwroot/css/theme.css:45`, `:54–57`, `:76`, `:187–200`, `:210–215`. Existing small chip text pairs measure 3.09:1 (OK), 3.74:1 (warning), 3.89:1 (bad), 2.91:1 (idle). Faint ink is 3.21:1 on white and 2.92:1 on paper. These ordinary small text treatments fall below a 4.5:1 target. See [reproducible pair calculations](evidence/contrast.json). This is a token-pair calculation; runtime overlays, opacity, and app overrides need separate verification. **Impact:** table labels, state chips, host names, and freshness metadata become difficult to read, especially on industrial displays and stale/dimmed content. **Recommendation:** add dedicated status text tokens, preserving brighter colors for dots where appropriate. Proposed foregrounds: OK `#236f34`, warning `#855000`, bad `#b42121`, idle `#535d66`; secondary/faint text `#626970`. On existing matching backgrounds these measure 5.55, 5.98, 5.69, 5.88, and at least 5.05 respectively. Audit green/purple accents independently. Keep textual status distinctions. **Acceptance:** every actual small-text foreground/background pair reaches 4.5:1 in both supported schemes and all states; focused control boundaries remain visible; no stale-state opacity reduces essential text below target. Owner: Theme first, then consumer exceptions. Suggested Impeccable commands: colorize, audit. ### DS-02 · P1 · TechField does not connect labels or errors to its control **Evidence:** `Components/TechField.razor:3–7` renders a sibling `