- RFC-002 Input:
- Token Dependencies updated to semantic aliases with primitives
- All tokens now map through color.surface, color.border, color.text, color.status
- No direct color references (e.g., semantic-red-500 → color.status.danger)
- Helper/error text uses semantic tokens
- RFC-003 Select:
- Token Dependencies updated to semantic aliases with primitives
- Dropdown, option, and error states use semantic tokens
- Selected option uses color.action.primary at 10% opacity
- No direct color references
- RFC-004 Card:
- Token Dependencies updated to semantic aliases with primitives
- Surface, border, text hierarchy use semantic tokens
- Shadow tokens mapped to elevation system
- No direct color references
- COMPLIANCE_MATRIX.md:
- Input: 33% → 83%
- Select: 33% → 83%
- Card: 33% → 83%
- All now have Governance ✅, Tokens ✅, Motion ✅, Accessibility ✅, AI ✅
Rationale: Semantic model first. Components never reference primitives.
Token contracts (purpose, allowed, forbidden) ensure correct usage.
Dark mode implementable via token swap without component changes.
- AI_DESIGN_PRINCIPLES.md:
- Restructured into 5 parts: A. Decision Process, B. Component Selection,
C. Token Usage, D. Design Review, E. Escalation
- All rules use RFC 2119 normative words (MUST/MUST NOT/SHOULD/MAY)
- Clearer escalation path: when to create DDR, when to flag uncertainty
- COMPLIANCE_MATRIX.md:
- Tracks readiness for all 29 components (Tier 1/2/3)
- 6 dimensions: Governance, Tokens, Motion, Accessibility, AI, QA
- Foundation documents tracked separately
- Button at 82% (reference for others)
- docs/platform/README.md:
- Reserved directory for cross-cutting governance
- Future: AI Governance, Product Governance, Review Process,
Quality Gates, Release Governance, Decision Frameworks
- Separates platform governance from design system
- LANDVEX_DESIGN_SPECIFICATION.md:
- Button renamed to RFC-001: Canonical Button Component
- Structured with: Cognitive Purpose, When to Use/NOT Use,
User Expectation, Interaction Contract, Failure Behaviour,
Accessibility Contract, AI Contract
- Sets standard for all future RFC component specs
Rationale: AI rules before components (AI writes components).
Compliance matrix makes progress visible. Platform governance
separates cross-cutting concerns from design system. RFC format
for components ensures production-ready specifications.
Bernt