brand-atoms
Brand guidelines, from PDFs into typed YAML — machine-consumable, composable atoms covering palettes, fonts, and glyph sets.
brand-atoms is a *-Atoms catalog in the Convergent Systems ecosystem. It defines what exists in its domain — typed, versioned, machine-readable, composable, and open — so runtimes (and humans) can stand on shared infrastructure instead of reinventing it.
Structure
brand-atoms/
├── ATOMS.yml # Catalog manifest
├── atoms/ # Reusable building blocks
├── brands/ # Compositions assembled from atoms
├── rules/ # Typed constraint vocabulary
├── schemas/ # Catalog-specific JSON Schemas
├── exports/ # CI-generated machine-readable exports
└── docs/ # Human-readable documentation
Atom types
palettefontglyph
Rule types
contrastRatiofontPairingforbiddenTreatmentnumericRange
Runtime consumers
aish, olympus
How to consume
Machine-readable exports are published in exports/ on every release:
exports/manifest.json— lightweight discovery (name, version, counts)exports/catalog.json— full catalog dump (every atom, composition, rule)
Exports are deterministic, signed, and versioned. See ATOMS.yml for the manifest and the conformance spec.
How to contribute
- Read
ATOMS.ymlto understand the catalog's atom types, compositions, and rules. - Add a new atom under
atoms/<type>/or a composition underbrands/<name>/. - Open a PR. CI validates the schema, references, and exports.
- Larger structural changes go through the XAIP process.
Ecosystem
- Federation: xdao.co · github.com/convergent-systems-co/xdao
- Spec: github.com/convergent-systems-co/atoms-spec
- Tools: github.com/convergent-systems-co/atoms-tools
- Umbrella: github.com/convergent-systems-co/atoms — all catalogs as submodules
- Other catalogs: brand-atoms, service-atoms, prompt-atoms, policy-atoms, identity-atoms, compliance-atoms, workflow-atoms, agent-atoms, knowledge-atoms, event-atoms, plugin-atoms
License
Apache-2.0 — see LICENSE.