Who is actually wearing the system.

A design system is only worth what its consumers have adopted. This page is the honest count: which repository wears which brand, how tokens reach it, and what still arrives by hand.

01 — Repositories

Six repositories, one system

Every one is its own git repository with its own remote. None are submodules, and there is no root package — so tooling that assumes a monorepo does not apply here.

RepositoryBrandTokens arrive byState
fooo-design-system source Publishes this site. Holds tokens/ and the build.
gabrielkroll-site Space hand-copied hex app/lib/tokens.ts, globals.css. On feat/hero-mesh, not main.
openorbit-site Space hand-copied hex Near-duplicate of the above. On feat/ai-sprint-reframe, not main.
mesoplus-site Agōn hand-copied, 26 inline defs No build step. Uses its own names — --space-text-dark-600.
mesoplus Agōn does not use FOOO The app. Vanilla JS, single file. Agōn grew here before it was a brand.
permaculture-analyzer No remote configured. Outside the system.

02 — The gap

Everything is importable. Nothing is imported.

The alias layer exists and every brand emits it. No consumer imports it yet, so every value in the four repositories above was typed by hand and will not move when Figma does.

What exists
dist/css/<brand>.public.css for Space, Agōn and Seed — a stable public API over the generated names, plus core.css holding the shared ramps. Guarded: the build fails if a semantic slot points at a token that no longer exists.
What is missing
Delivery. dist/ is gitignored, so those files exist only where the build ran. Two candidates, neither built: the build writes each consumer's file across sibling directories, or a CI job commits it into each repository. See PIPELINE.md.
What adoption costs
Per-repo hex-to-var swaps are the long pole, not the plumbing. gabrielkroll-site and openorbit-site carry near-identical :root blocks, so that is one diff applied twice. mesoplus-site is 26 definitions in one file.

03 — This site

The documentation is not a product

design.openorbit.studio wears none of the three brands. It is a tool for reading the system, not an example of it.

Its chrome is its own surface. Light ground, Inter for reading, IBM Plex Mono for labels and every number on the page. That last choice contradicts Core 2.0, which rations mono to code, data and measurement and moved eye brows to Inter — and it stands, deliberately: this site is closer to an instrument panel than to a brand surface, and nearly every label on it sits beside a token value.
What it does follow. Core's geometry — the scale, the 942 measure, the containers. So the site is built on the system without claiming to be a specimen of any brand in it.