brand-system-living-document

name	brand-system-living-document
description	Use when documenting brand decisions. Brand system docs evolve with the product; treat as living, not frozen.

Brand System Living Document

Brand book is alive. Update with each decision. Single source of truth in repo. Frozen brand books die.

Brand doc structure

/brand/
├── README.md (overview)
├── tokens.css (design tokens)
├── typography.md (type system)
├── color.md (palette + usage)
├── components.md (button, card, etc.)
├── voice.md (brand voice + copy)
├── photography.md (treatment + sources)
└── decisions.md (decision log)

Decision log pattern

Date-stamped decisions:

## 2026-05-01: Adopt orange accent

**Context**: needed accent color for CardPrepAI
**Options considered**: orange, blue, navy
**Decision**: orange #e85d2c
**Rationale**: distinct from X3 ecosystem, warm + premium feel
**Trade-offs**: requires contrast adjustment on cream

Update cadence

1. Edit docs in PRs alongside code changes
2. Quarterly review: prune outdated patterns
3. Major change = decision log entry
4. Reference docs from design files (Figma comments link to git docs)
5. Onboard new designers: docs are step 1

Where this fits in the X3 empire

Brand system documentation for CardPrepAI.