The card said "routine cleanup, risk low." The reviewer approved in nine seconds. Then the agent touched 1,800 records that were never in the plan.
I use that scenario in design reviews. It is constructed, not a customer story. The failure mode is ordinary though: the card described the task, not the change.
So what did the reviewer actually consent to? Nobody could say. That is a design bug, not a model bug.
Today I'll build the smallest gate that fixes it. A card carries the scope delta. Consent binds to that exact delta. Missing evidence blocks the run, and the block names the missing field.
It is a tutorial, so we go from empty folder to a verification script that fails loudly.
Stage 0: Pick a place to run it
You need two things before code: an endpoint that returns a plan, and a host that stays up while you click.
For the endpoint I'm using MonkeyCode's free model access, and for the host its free server option.…