| name | Helmryth | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| description | A light-first editorial instrument panel for persistent, accountable digital operators. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| colors |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| typography |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| rounded |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| spacing |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| components |
|
Helmryth is a light-first operating surface for autonomous work. Its identity combines the precision of an instrument panel with the humanity of an annotated field notebook. The interface is dense enough for serious work but never visually anxious. The memorable element is the score line: a fine, living signal connecting operators, gates, tools, and outcomes.
The master tagline is “The work moves. You hold the helm.” Supporting copy is factual and active: persistent operators, real tools, visible decisions.
Warm mineral neutrals dominate. Vermilion is command: selected actions, consequential buttons, and the Helmryth mark. Petrol is signal: connected, live, streaming, or focused. Neither accent may become a page background. Semantic fills are pale and bordered; status must also include iconography or text.
Dark mode is not part of the initial Helmryth identity. Never use pure black, pure white, purple-blue gradients, neon, or glow.
Geologica gives headings a shaped, engineered voice; Atkinson Hyperlegible Next keeps long workstreams readable and accessible. Product UI uses a five-step hierarchy, not a cloud of near-identical text sizes. Labels may use uppercase only when shorter than three words.
Do not use Inter, system UI, Space Grotesk, Instrument Sans, monospace-as-technology, gradient text, or oversized marketing typography inside the application.
The application uses an asymmetric three-zone shell: a narrow score rail, a flexible roster/workstream column, and an optional trace/workbench surface. Separation comes from fine rules and rhythm, not nested cards. Use the 4px spacing system and favor gap over margins.
On narrow screens, the score rail becomes a compact bottom score and secondary surfaces become full-screen sheets. No critical action disappears.
Depth is quiet and physical. Use a 1px warm rule, a subtle tonal surface shift, and at most one low-opacity shadow for floating menus. Modals are reserved for destructive confirmation, authentication, or truly blocking gates. No glassmorphism or decorative blur.
Corners are tailored rather than pillowy: 6px controls, 8–12px work surfaces, pills only for compact state chips. The Helmryth mark and operator sigils use square geometry, clipped corners, and braided diagonals. Avatars are abstract instruments, never faces, animals, blobs, or placeholder initials in circles.
The score rail is the primary global navigation. Each destination pairs a line icon with a direct Helmryth term: Roster, Crews, Cadences, Capabilities, Operations map, and System. Active state uses ink weight, a small vermilion notch, and an accessible label—not a glowing background.
Every operator receives a deterministic sigil composed from a frame, weave, and pulse. Activity changes the pulse pattern and accessible status label, not the identity. User-supplied portraits remain supported but are cropped into the same tailored frame.
Messages sit directly on the canvas with alternating alignment, measured line length, and sparse tonal plates. Tool activity, files, decisions, and gates use distinct document-like structures. Avoid generic rounded chat bubbles for every event.
Gates state the requested action, resource, consequence, and requesting operator before controls. “Allow once” is the emphasized action; persistent grants are progressively disclosed.
Every empty state teaches one concrete next action and shows an example grounded in the current surface. Never use “Nothing here yet,” generic sparkle art, or fake sample metrics.
- Do make running work, waiting work, and blocked work distinguishable without color.
- Do use precise, accountable language and visible consequences.
- Do preserve keyboard operation, focus visibility, reduced motion, and 4.5:1 text contrast.
- Do keep legal attribution and third-party notices accurate.
- Don't use “bot,” “assistant,” “copilot,” “AI-powered,” “supercharge,” “unlock,” or “magic” in product copy.
- Don't use sigil faces, emoji icons, card grids, glass, glow, dark command-center styling, or purple-blue gradients.
- Don't hide complexity behind vague labels; use progressive disclosure with exact wording.