Design docs

chart-foundations.md

Chart foundations doctrine

The native-SVG chart family's shared rules — palette, axes, motion, tooltips, accessibility.

components.md

Components doctrine

What ships today, the pattern-coverage map ("want X? use Y"), and the guidance for adding a new component.

compositions.md

Compositions — patterns worth knowing

The "X + Y composes well" doctrine — layout shells, chart surfaces, chat, suite chrome, cross-app navigation.

kit-pipeline.md

Kit pipeline — framework targets

The two-tier doctrine: deterministic token emitters (C#, React, WordPress, Power BI) vs component ports — the port ledger, the drift bot, and the superPOD review loop.

palette.md

Palette + visual identity

TTI palette reconciliation across PPTX/PDF sources, visual identity cues to preserve, relationship to TAMUS.

platform-awareness.md

Platform awareness doctrine

The two-layer model for web + Tauri desktop + mobile chrome, and the visual languages tux deliberately rejects.

roadmap.md

Roadmap

What's missing from tux today, ordered by impact, plus the carry-forward list of small deferred capabilities.

tauri-bindings.md

Tauri bindings reference

Which Tauri capabilities each platform-aware component needs, and the reserved future surface.

tux.md

tux — design system

Principles, stack, signature moves, theme variants, four-family typography rule, three section styles. Read first.

unification-plan.md

Unification plan — one suite, one system

The cross-portal unification doctrine: two-shape identity rule, one-chrome-many-voices, registry law, distribution artifacts, execution log, open decisions.

visual-language-evolution.md

Visual language evolution

Dated batches recording how the visual language has shifted — what changed, what was rejected, and why.