How to read the trace
Four receipts. One claim.
- 01DecisionWhat survived
- 02RuleWhat governed it
- 03ConstraintWhat the product required
- 04EvidenceWhat cleared it
The trace
Three consequential decisions
Enough to audit the result. Not a transcript of every style property.
Decision
Complete state model
The Orders screen includes default, loading, empty, and error states instead of treating the happy path as the whole product.Rule0cd0438deeux-baseline-check
“Every screen ships with all states covered. No exceptions. This is the minimum bar.”
Source constraintloop-demo/README.mdProduct requirement
“Task: an ‘Orders’ admin screen with default/loading/empty/error states, gated at 390 / 768 / 1280px.”
Evidence ReviewedRendered receipts
Decision
Mobile touch targets
Interactive controls were enlarged until every measured mobile target cleared the 48px gate.Rulee2b379b311design-review / mobile
“Touch targets are at least 48×48px, with enough spacing to avoid mis-taps.”
Source constraintpresets/utilitarian-app.mdProduct requirement
“Touch targets and responsive behavior handled cleanly.”
Evidence ReviewedRendered receipts
Decision
Restrained hierarchy
The final screen uses spacing and typography for hierarchy instead of decorative color noise.Rule546806cbfbdesign-review
“Typography check: is hierarchy clear without leaning on color?”
Source constraintpresets/utilitarian-app.mdProduct requirement
“Hierarchy through spacing and type before color.”
Evidence ReviewedRendered receipts
The standard
Why. Which rule.
What proves it.
A reviewer should answer all three in under two minutes, without asking the agent to reconstruct its reasoning.