@getbourdon/design-system

The one design system for every Bourdon product: the engine's own surfaces, the Bourdon phone app and Bourdon Meetings all read these files. Nothing else in any repo may restate a colour, radius, shadow or type face.

| File | Consumer | How it is read | |---|---|---| | tokens.json | the source of truth | change a value here first | | web/tokens.css | web, desktop | @import / import as text | | kotlin/BourdonTokens.kt | Android (Compose), package ai.bourdon.design | a Gradle java.srcDir pointing at kotlin/ | | swift/BourdonTokens.swift | iOS (SwiftUI) | an XcodeGen source path | | fonts/*.ttf | every client | copied or bundled at build time; each face ships with its licence |

Consuming it

• Inside the bourdon repo, read it by path: packages/design-system/....
• In any other repo, pin the published package ("@getbourdon/design-system": "1.0.0") and point every consumer at node_modules/@getbourdon/design-system/.... Do not copy files out of it; a copy is exactly how the palette once drifted across three repos.

Changing it

1. Change tokens.json, then the sibling files by hand, in one PR in the bourdon repo. tests/test_design_system.py fails if any sibling disagrees with tokens.json, if an action colour stops meeting WCAG AA, or if a font's real PostScript name stops matching its filename.
2. Bump version (semver: a removed or renamed token is a major bump).
3. Publish, then bump the pin in each consuming repo.

The fonts are licensed separately under the SIL Open Font License; see fonts/LICENSE-*.txt.