Philosophy

Make the important things readable

High contrast, compact layouts and clear hierarchy support fast scanning. OPERATOR Sans carries interface text; Mono aligns data. Component headings and actions use capitals. Decoration must earn its place.

Be direct

Use specific labels and visible error states. Keep critical alerts present until acknowledged. Give operators the information needed to act, without repeated instructions or unnecessary steps.

Build from the system

Foundations → core controls → components → patterns.

Foundations define typography, color, spacing, focus and motion. Core controls handle shared interactions. Larger components reuse those controls; patterns connect their public APIs to application data. Add reusable capabilities at the appropriate lower layer, rather than copying controls inside a pattern.

The documentation previews the same source distributed to consumers. OPERATOR provides component code and rendering contracts; accessibility primitives supply keyboard and focus behavior. Applications own transport, authorization, persistence and authoritative outcomes.