Speaker

In a compound product that spans multiple domains, even aligned components let token usage and component roles drift before anyone notices.

Writing conventions in docs and fixing them in review still cannot keep up as the codebase grows, and a component catalog cannot inspect that drift.

So we made the design system itself a schema-based contract, and with Schema-Driven UI the same schema can reproduce the same frontend.

Raw values fail typecheck, and cross-layer imports fail dependency lint. Human review is left for judgments machines cannot make. This talk is about protecting frontend implementation with a contract.