Knovaryn design system¶
The design system keeps every Knovaryn surface — README, documentation site, diagrams, screenshots — saying the same thing in the same visual voice.
The voice follows the brand's one sentence: every training example, traced to its source. Visuals show provenance routes (segmented evidence), quality gates (the ring), and verified output (solid strokes). Nothing decorative outranks clarity.
What lives here¶
| Page | Contents |
|---|---|
| Brand foundations | Identity attributes, logo system, voice |
| Color | Palettes, neutral scale, semantic status, contrast rules |
| Typography | Typefaces, type scale, usage |
| Spacing and layout | Grid, spacing scale, content widths, breakpoints |
| Components | The shared component vocabulary |
| Icons and illustrations | Icon style, illustration rules |
| Diagrams and data visualization | Diagram grammar, chart style, benchmark graphics |
| Accessibility | WCAG AA expectations per surface |
| Motion | Durations, easing, reduced-motion contract |
Where tokens are defined¶
Machine-readable tokens live in
docs/assets/design-system/tokens.css
as CSS custom properties (--kn-*) and are loaded by the site through
mkdocs.yml's extra_css. The documentation pages describe those tokens;
when a value changes, change the CSS file and the page together.
Who consumes it¶
- Contributors writing or editing docs pages, diagrams, or console output.
- Generators: everything under
scripts/visuals/reads these values so brand assets stay reproducible (see brand foundations). - Reviewers checking a proposal against accessibility before merge.
Ground rules¶
- Truth first — no visual may imply a claim the claim matrix does not back.
- Provenance is the motif — segmented spans, gates, solid verified strokes; not clouds, robots, or magic sparkles.
- Contrast over aesthetics — if a color pairing fails WCAG AA, the pairing is wrong (see color).
- Static fallbacks exist — anything interactive degrades to a readable static equivalent (motion, accessibility).
- No invented numbers — charts carry real values from committed benchmark runs with their context labels (data visualization).