# Constraints Validated At Definition Time Propagate Not Recur ## Claim Moving a quality check to the point where a value is defined, rather than where it is used, converts an N-times-repeated judgment into a once-made decision that everything downstream inherits. <!-- atomicity: 1 idea ✓ --> ## Scope & conditions - Requires that the definition point actually constrain the use point — a token designers can override locally provides only a default, not an inheritance guarantee. - Holds strongly for contrast, type scale, and spacing rhythm. - Holds weakly for anything context-dependent — contrast on a photographic background can't be fully settled at the token layer. - Generalizes well beyond design: schema constraints vs. per-query validation, type systems vs. runtime checks. ## Evidence Penpot's system library file documents design tokens by demonstrating them and includes a built-in contrast test, so accessible color pairings are decided once by the person who owns the tokens rather than re-argued in every component or PR. The presenter also built a personal accessibility-checklist plugin for gaps the built-in tooling didn't cover, illustrating the same principle applied by an individual practitioner rather than the platform. ## Links - [[Visual Thinking MOC]] — moving a check to the definition point converts N validations into one - [[3. Resources/Permanent Notes/Abstraction Layers Convert Into Coordination Cost]] — because extends: from the same source, the companion argument about where coordination cost lives in a design system - [[3. Resources/MOCs/AI & the Future of Knowledge Work MOC]] — because applies-in: shift-left validation is the same logic behind moving quality checks earlier in any generative or reviewed pipeline ## Tests / falsifiers - Compare audit findings across two design systems with matched scope, one validating contrast at the token layer and one only at the component layer; the claim predicts fewer contrast-related findings for the former. - Find a token-layer constraint that designers routinely override locally without consequence — would show the inheritance guarantee doesn't actually hold in practice for that constraint type. ## Maintenance - Last tended: 2026-08-16 - Next review: 2026-11-16 ## Source - [[3. Resources/Literature Notes/A Developer's Guide to Penpot (Design Tokens, Grid, Flex & Code)]] — the token-layer accessibility validation demonstration.