Postmortem

Anatomy of a false claim

One sentence on the aria page claimed a motion audit that had never run at scale. This is the full anatomy: the sentence, the audit it summoned, and the 63 scenes behind it.

Intermediate1 min read (computed · recorded 8)updated 2026-09-12auditclaimsmotion

by Motif Editors

revised 2026-09-12 — First publication in the suggestions-100 backlog batch.

Part 1 of 6 in How a build tells the truthWhat a build cannot see →

Key takeaways

— A claim on a page summoned the audit that checked it — write the claim, then build the check.
— The gap measured 63 scenes without a reduced-motion branch; the number came from a scanner, not a guess.
— The fix was a hook, not sixteen copies of the same media query.

The sentence

The aria page said the site audits its motion — a sentence in the conditional mood that read like a statement of fact. Nobody had lied, exactly; the audit existed as an intention. But a reader cannot tell an intention from a record, and the page did not help them try.

The audit the sentence summoned

Writing the audit was the only way to keep the sentence. It walked every scene module, matched each one against the signals that mean a component animates — animation properties, repeat values, transitions — and split the result into what a stylesheet can stop and what JavaScript has to stop, because only the second group can honestly claim a branch.

The 63

Sixty-three scenes had no branch at all. The number was printed on the page with the first unguarded scene named per module — a gap you can start working from, not a rounding error to be ashamed of. The hook that fixed them is one function in scene-kit, and the audit now re-derives the count on every batch.

Practise the lesson

Theory sticks when you ship it. These original Motif assets put this guide's lesson to work — open one and copy it into your own page.

Audit Ring with Threshold Tickspractice Inline Status Bannerpractice Shake-on-error Fieldpractice

Keep learning

All guides Try the interactive Lab