AI ships interfaces faster than teams can review them.
A model can restyle every screen in one commit. The direction you chose — the typography, the color system, the identity — erodes one plausible-looking edit at a time. Screenshot reviews don't scale, and a second model's opinion is not evidence.
One chain, from intent to proof.
- RouteRefine, explore, reconstruct, reimagine, or verify — the narrowest lane wins.
- ShapeCompare three structurally different directions on the same real content.
- BuildImplement in your stack, through semantic tokens, with real states.
- SeeInspect rendered mobile and desktop pixels; fix the largest gaps first.
- ProveDeterministic gates: tokens, contrast, source rules, accessibility, screenshots.
- PreserveTaste Lock fingerprints the approved identity; drift becomes a finding.
A drift is a finding, not an opinion.
One hardcoded color slipped past a token system. Here is the actual output — file, line, rule, and the exact repair — not a score, not a vibe.
❯ dk verify
✓ token contract 10 contrast pairs pass (light+dark) · 72 tokens
✓ SSOT sync tokens.css in sync with the SSOT
✗ anti-AI-slop 1 findings
✗ index.html:25:12 slop/hardcoded-color
Hardcoded color #0071e3 — this is really var(--color-brand-accent)
❯ dk fix --slop
· index.html:25 #0071e3 → var(--color-brand-accent)
❯ dk verify
✓ All passed — 0 errors, 0 warnings
1 files scanned · 10 contrast pairs pass · tokenHash a5ed77f0Reproduce it yourself: npm run demo — byte-for-byte restoration, then dk benchmark — 10/10 injected drifts detected and recovered.
Or watch it happen: the 31-second film of this page being designed, failing its own gates, and locking.
Approve once. Every later edit answers to it.
directionHash
Fingerprints the approved identity — thesis, composition, typography, form, motion. Copy can grow; the identity cannot silently change.
bindingHash
Fingerprints what the semantic roles resolve to, in light and dark. Rebind the accent and the build fails until a human signs a reason.
Approvals live in an append-only, hash-chained ledger: who, when, why, and the evidence at that moment. Deleting or rewriting history is itself a detectable finding.
This page is governed by the tool it presents.
The direction below is this page's own contract. The hash is this page's own token build. The green line is this page's own verification. Nothing here is a mock-up.
- direction
- “Editorial Ledger” — a quiet editorial ledger where every claim sits beside its proof.
- signature
- Numbered margin anchors bind each narrative band to a verifiable artifact.
- avoid
- generic bento grids · gradient glow · vanity numbers · screenshot walls
- tokenHash
cf1699f7e56cf547- verify
✓ All passed — 0 errors, 0 warnings- taste lock
directionHash 1e84700a · bindingHash 447a004f · apr_b88588db21e73e96