ADR 0010 — Visual Identity v2 (warm ink/cream system)
The Cursor-derived design language replacing Kredal Navy, and what stayed fixed.
- Status: Accepted
- Date: 2026-07-16
Context
Kredal's v1 identity ("Kredal Navy", ADR 0002/0005 era) read as conventional
enterprise fintech. For Hub71 and pilots, the product needed a more distinctive,
tool-grade identity. A full design-token extraction of cursor.com (live CSS
custom-property audit + computed-style measurements) provided a proven, warm,
editorial system: paper cream #f7f7f4 / warm ink #26251e (dark canvas
#14120b), orange accent #f54e00, pill buttons at regular weight, tint-ladder
cards, and a snappy 0.14s motion standard.
Decision
Adopt Visual Identity v2: the warm ink/cream token system codified in the
root design.md, applied across the marketing site, app dashboard, style guide
(/styleguide), docs accents, and a new K-check monogram logo (a geometric K
whose lower leg resolves into a checkmark). Typography moves to a
Cursor-derived scale on Inter with tight tracking; code stays on Geist Mono.
What did not change: risk-colour semantics (ADR 0005). riskLevel(score)
remains the single band→risk mapping; risk colours mean risk only. Hues were
re-mapped to the v2 palette (low #1f8a65, medium #b45309, high #cf2d56,
lightened variants in dark mode) with AA-checked foreground/tint pairs.
Consequences
- Positive: distinctive, coherent brand across landing/app/docs; a living
/styleguide; agent-readabledesign.mdkeeps future UI work on-system. - Negative: navy
#1e3a8ais retired — any lingering usage is a defect. Orange fails AA for small text on cream, so it is restricted to CTAs, large text, and icons (rule recorded in design.md §5).
ADR 0009 — AI extracts, deterministic rules decide
How the Gemini AI layer coexists with the auditable scoring engine.
ADR 0011 — Platform admin via allowlist + service-role reads
Why /admin gates on a SQL-only platform_admins table and reads through the service-role client instead of new RLS policies.