Write the contract first
When approval became the work
During the BuilderBob migration, I kept getting pulled back into routine work I had already authorized. Deleting the old copy after a move was a decision worth bringing back to me. Asking again about work I had already handed over gave me another task without giving me a new decision.
Write down who decides
Before giving an agent a task, name the work it can finish, the decision you are keeping, and the check you expect it to run. Give it an example close enough to that boundary that you can tell whether you agree.
A requirement in a shared model
In my instructions for the computable systems engineering project, routine draft repairs can proceed. The engineer owns the accepted units and thresholds. An agent can repair a draft and run the checks. If it thinks a different threshold would make more sense, it can propose that change and explain why.
Try a handoff
Give a classmate a draft requirement for a pump and a short contract for editing it. Include a spelling error and a pressure limit that looks implausible. Ask them to mark what they would fix, what they would ask you, and how they would check the edit. Revise any instruction you understood differently.
What this leaves open
A written contract gives me something to review when the agent gets the decision wrong. Access to the machine still depends on the permissions actually in place.