Repo: brand

Status: Accepted

The design system — logo assets, colour/type/space tokens, and usage docs, packaged as @lemonfiber/brand. Consumers take it as a commit-pinned git dependency; nothing is published to a registry yet.

Implements: 60-brand, the design-token contract.

---

What this repo is

The single source of the brand: SVG marks, tokens as CSS + JSON, and the detailed usage docs. Pull assets from here rather than re-drawing or re-exporting — that is the repo’s whole purpose, and the reason it’s a repo rather than a folder in lemonfiber.

lemonfiber’s web UI consumes it as a dependency pinned to a commit (contract); the marks are also referenced where the web UI shows a logo.

Layout

brand/
├── assets/logo/        SVG marks — proprietary (see licence)
├── tokens/
│   ├── tokens.css      CSS custom properties
│   └── tokens.json     the same values as data
├── .docs/
│   ├── colour.md       full palette + rules
│   ├── typography.md
│   ├── logo-usage.md   clear space, minimums, pairings
│   └── asset-sheet.html  contact sheet
├── package.json        @lemonfiber/brand
├── CHANGELOG.md
├── LICENSE             marks — proprietary
├── LICENSE-tokens      tokens + docs — open
└── README.md

The split licence

This repo is where the project’s “open source, protected brand” position becomes concrete (licence rationale):

This is the standard pattern — Rust, Mozilla and Python all protect marks inside open projects. The LICENSE file governs the marks; LICENSE-tokens governs the rest, and the README states the split at the top so no one mistakes the marks for freely reusable.

What the spec owns vs. this repo

The rule of thumb matches every other repo: what and why, and cross-repo contracts, are the spec’s; the detailed how is the repo’s.

CI

The check compares colours only: the font, size, space and radius groups, the stylesheet’s --lf-color-text and the ink theme are not compared, so ARCH-R38’s identical values are checked for colours alone. The contrast half computes the ratio of each of those five colours on paper and fails on one below AA; no other surface, and neither theme’s other pairings, are measured, so it covers part of what ARCH-R40 asks. A recolour that looks fine and fails that meter is caught here, not in the web UI.

Publishing

@lemonfiber/brand is not published to a registry and has no tags, so consumers pin a commit. A consumer moves the pin deliberately (cite GOV-R12) to pick up a brand change — the token contract keeps brand and binary decoupled, so a recolour never surprises a shipped lemonfiber.

Governing aesthetic change

Brand is judgment-heavy. The governance resolution: changes within the rules (a new export, a recolour inside the palette) cite GOV-R12; changes to what the rules permit are DES-R changes following the normal lifecycle. This keeps the repo under governance without pretending aesthetics are requirements.

Requirements

Related

• 60-brand/ — the brand section
• design-tokens contract
• licence rationale
• ADR-0004 Four-repo split — why brand is its own repo