Proof system
Inspect calculated component checks and their coverage.
Core principles
- Read the evidence type and coverage with the pass or fail result.
- Use calculated checks alongside browser tests and accessibility review.
Model
- Component registrations provide fixtures for declared recipe cases.
- Fixtures report evaluated, unsupported, and unresolved checks.
Use in your app
- Inspect failures at every requested width before changing a recipe.
- Use token and CSS-variable references to trace a failed calculation.
Verification scope
- Component fixtures use mathematical estimates. They do not collect browser evidence or certify accessibility.
- Browser tests cover their specific rendered scenarios. They do not establish behavior for every theme or state.
Token notes
- Fixture results, examples, and component APIs come from the public component artifacts.