It expires in weeks, not years
A prompt that worked in January behaves differently in July. The model changed underneath it and nobody told you.
The verification layer for AI knowledge
Doestep is the only place that proves what still works — on this model, right now — because Doesteppers ran it and logged the result.
Extract structured data from a messy invoice · v3
A new model shipped. The badge started unverified — then Doesteppers re-ran it and it went live. That flip is the whole product.
The problem
A prompt that worked in January behaves differently in July. The model changed underneath it and nobody told you.
“I built an agent that 10x’d my workflow.” Great — can anyone else run it and get the same result? Usually not.
The internet is full of AI skills nobody can verify. Claims are cheap. A logged reproduction is not.
How it works
A playbook gets proven, a new model breaks it, the community proves it again. The model-release event is the heartbeat.
Read the loop in depth on how it works →
The badge, up close
This is something no tutorial site, GitHub repo, or Discord has: a status that’s computed from real reproductions and can’t be written by hand. Conflicting results are shown, never hidden.
The states
Same object everywhere — on the site, in a README, in a tweet. Mono for the data, status color for the fact.
State of What Works
When a new model ships, every affected playbook flips to “not yet verified.” We publish the only report built from real reproduction data — what survived, and what quietly broke.
the moment a model ships
No one edited anything. The evidence just aged out from under it.
Who's a Doestepper
A Doestepper is anyone who runs the thing and logs the result. You don't join a space or a channel — you join people, by the tools you build with and the work you do.
412 Doesteppers verified this on Sonnet 5 — not 412 “members.”
Join the first Doesteppers. When the badges flip, you'll be the reason they flip back.