← back to the test

file a brake report

One dead brake is a shrug.
Ten thousand, filed the same way, is a record.

You ran the test: found the brake, set it, closed the app, reopened it. Whatever happened, file it here. This builds a structured report, the same shape every time, so a scattered hashtag becomes something you can count: which platform, which control, whether the choice held.

That consistency is the point. A pile of look-alike reports is the raw material for the deception and unfair-practices case regulators and state attorneys general are already building: not a claim that a feed is bad, but proof that a control the platform offered did not do what it said. The companion policy paper calls that control integrity; this is where you document its absence.

before you file

Report the setting and the behavior, never a person. No usernames, no DMs, no faces, no kids, no locations. Aim at the loop, not each other.

This form stores nothing. It builds a structured post for you to share, so ten thousand reports read the same way. Keeping your data without asking would be the exact thing we're asking platforms to stop.

what happened when you set it, closed the app, and reopened
your report
Pick a platform, a brake, and what happened. Your report builds here.
post on X →or paste it anywhere with #WheresTheBrake

Want to see the test written down so everyone scores it the same way? Read the brake scorecard. Honest note: this page stores nothing, so it cannot itself tally the reports. A central, submittable dataset is the movement's next piece of infrastructure, and it needs a backend and a published data-retention and moderation policy before it should ever hold a single submission.