What has actually shipped

QR codes, and four marketing sections that ship no JavaScript

Printable QR codes for every product, and the sections a marketing site is expected to have — a closing call to action, an FAQ, a process explainer and social proof — built natively on the token layer rather than pasted from a template.

• A QR code per product, encoded server-side and decoded in a test that asserts the exact URL
• Closing CTA rendered by the page shell with per-page copy, so no two pages repeat themselves
• FAQ answers read from the assistant's knowledge base, so the page and the bot cannot disagree
• Social proof is the five live products, linked — no invented logos, testimonials or user counts
• All four are server components: the JavaScript budget did not move

AI assistant, full site, and accessibility pass

An assistant that answers questions about the company, grounded on a knowledge base generated from the design system's own source so it cannot drift from what the code does.

• Streaming answers from Claude Opus 5, with prompt caching on the knowledge corpus
• Works with no API key at all — deterministic retrieval over the same corpus, same UI
• ⌘K / Ctrl+K from anywhere, with focus trapping, focus restore and a polite live region
• Product links now point at the live deployments
• Products, platform, design, about, docs, contact, and the legal pages

Design tokens and theme engine

The foundation: a product's entire visual identity reduced to one hue angle, and an admin-controlled theme engine that rethemes the ecosystem without a rebuild.

• OKLCH ramps specified in contrast space — accent-600 measures 4.60:1 in all six identities, a 1.0003× spread
• Runtime theming as a sub-2 kB override patch on :root, inlined during SSR so there is no flash
• Reduced motion as a single variable that collapses every animation, including future code
• 19 tests covering contrast parity, gamut mapping, schema bounds and CSS injection resistance
• Nine token-driven UI primitives and the company site

Command palette and data visualisation

The two highest-leverage shared components. One keymap across five products is what makes them feel like one tool rather than five tabs, and charts are the hardest thing to retrofit consistently — so they should not wait.

Platform kernel

Identity, organisations, RBAC, billing, usage metering and an audit log. Schema first, because five products sharing a tenancy model that was retrofitted is a two-year problem. The organisation is the tenancy boundary, not the user.

AI gateway

Routing, budget caps, a versioned prompt registry and server-side tool-call re-authorisation, so no product holds a provider key and no product pins a model id.