Design Decision Records (DDRs)
Records of design choices: brand identity, visual language, UX patterns. Each DDR captures what was picked, what was rejected, and why — so future readers don't re-litigate settled ground.
Why a separate series from ADRs
docs/architecture/decisions/adr-* covers system-shape decisions: data model, storage, ingestion, deployment. Those decisions are typically driven by performance, correctness, or operational constraints.
docs/design/decisions/ddr-* covers visual and experiential decisions: marks, lockup rules, copy framework, page composition. Those decisions are driven by brand strategy, trademark constraints, and user-perception arguments.
Mixing the series obscures both. Keeping them separate lets each evolve at its own pace, and lets reviewers stay in the right register when they read.
Format
DDR files follow the same structure as ADRs:
# DDR-NNN — Short title
**Status:** accepted | superseded | rejected
**Date:** YYYY-MM-DD
**Supersedes:** (DDR-MMM, if any)
## Context
What problem are we deciding on?
## Decision
What did we pick?
## Alternatives considered
What did we reject, and why?
## Consequences
What does this constrain going forward?
Index
| ID | Title | Status |
|---|---|---|
| DDR-001 | Bracket-S monogram as the SecurityV0 mark | Accepted |