Where you sign off
The stations stay. The moments move.
Where in your flow is the moment you sign off? The cycle stays as it is. Per workflow, only the place where Judgment happens moves.
Left the steps as they happen in everyday work, right where the framework sits. Stations can come back, because real work does not run in a straight line.
The author is whoever signs off, in their own name, that the conditions are met.
1Solo, straight on main
You
Pick up the task: ticket, idea or bug.
Intent · Opening Line
One sentence on what done means, and the risk level.
You
Decide what the agent gets and what you do yourself.
Orchestration · Delegation Matrix
What you do yourself, what you delegate, what you grow.
You
Write the failing test or the expected result first.
Verification · Prophylaxis
Set the criterion before you see the output.
Agent
Implements in the editor. You read along between runs.
Orchestration · Between Turns
No second hard task between agent runs.
You
Read the diff. Run tests, linter and type check.
Verification · Evidence
Proof in proportion to the risk. "Tests green" alone is not the criterion.
You
Self-review the diff once more, as if it were someone else's.
Judgment · Blunder Check
Name one place where it could be wrong, then check it.
You
Commit: your "yes" to the agent.
You sign off here
Judgment
The one signature. There is no second key.
You
Push to main.
You
End of day.
Accountability · Post-Game Analysis
A short look back in the evening: what did I think through myself today?
There is no second key. Your own self-review carries everything.
2Solo with a PR
You
Create the issue with the target state.
Intent · Opening Line
One sentence on what done means, and the risk level.
You
Create a feature branch off main and brief the agent.
Orchestration · Delegation Matrix
What you do yourself, what you delegate, what you grow.
You
Write the test or the acceptance check first.
Verification · Prophylaxis
Set the criterion before you see the output.
Agent
Implements on the branch in small commits.
Orchestration · Between Turns
No second hard task between agent runs.
You
Push, open the PR, wait for CI.
Verification · Evidence
Proof in proportion to the risk. "Tests green" alone is not the criterion.
You
Review the PR diff yourself, line by line.
Judgment · Blunder Check
Name one place where it could be wrong, then check it.
You
Merge.
You sign off here
Judgment
CI
The pipeline deploys.
You
End of day.
Accountability · Post-Game Analysis
A short look back in the evening: what did I think through myself today?
For solo work only. In a team this is no model: a second account there bypasses the four-eyes principle.
3Team, PR flow
You
Pick up the issue and clear up open questions.
Intent · Opening Line
One sentence on what done means, and the risk level.
You
Branch off main. Brief the agent: scope, files, limits.
Orchestration · Delegation Matrix
What you do yourself, what you delegate, what you grow.
You
Write the tests or acceptance criteria first.
Verification · Prophylaxis
Set the criterion before you see the output.
Agent
Implements in small commits. You stay at the keyboard.
Orchestration · Between Turns
No second hard task between agent runs.
You
Push, open a draft PR, wait for CI.
Verification · Evidence
Proof in proportion to the risk. "Tests green" alone is not the criterion.
You
Review your own diff before anyone else sees it.
Judgment · Blunder Check
Name one place where it could be wrong, then check it.
You
Mark the PR "Ready for review".
You sign off here
Judgment
Your key. The burden of proof is with you as the author.
Reviewer
Reads the diff, comments, approves.
Judgment
The second key. The reviewer checks your check, not only the code.
You
Resolve the comments, merge. The pipeline deploys.
You
End of day.
Accountability · Post-Game Analysis
A short look back in the evening: what did I think through myself today?
Two keys. The burden of proof is with you as the author, the reviewer checks your check.
Two keys
In a team the move needs two keys, and they are not the same key.
1 · Author
Ready for review
You carry the burden of proof: criteria, evidence and your named weak spot are in place before anyone else looks.
2 · Reviewer
Approve (countersign)
You check the check: is the proof sound, not only whether the code looks good.
4The agent opens the PR
You
Write the issue: target state, non-goals, risk level.
Intent · Opening Line
One sentence on what done means, and the risk level.
You
Add to the issue which areas the agent may touch and where it stops.
Orchestration · Delegation Matrix
Orchestration sits in the issue. After the hand-off you only have the PR.
You
Add the acceptance criteria or tests to the issue.
Verification · Prophylaxis
Set the criterion before you see the output.
Agent
Picks up the issue, works on a branch, opens the PR.
Orchestration
CI
Runs on the PR.
Verification · Evidence
Proof in proportion to the risk. "Tests green" alone is not the criterion.
You
Review the PR as its author, not as a bystander.
Judgment · Blunder Check
The risk: you feel like a reviewer. You are the author.
You
Take over the PR: mark it "Ready for review" or approve it yourself.
You sign off here
Judgment
Reviewer
In a team: review and approve, as in the team flow.
Judgment
The second key.
You
Merge. The pipeline deploys.
You
End of day.
Accountability · Post-Game Analysis
A short look back in the evening: what did I think through myself today?
Intent and Orchestration sit in the issue. The risk: you feel like a reviewer instead of the author.
5Reviewer of someone else's AI PR
You
Read the PR description and the linked issue.
Intent
Are the Opening Line and the risk level there? If not, ask the author.
You
Read the tests first, then the code.
Verification · Prophylaxis
Check the check: were the criteria set before the output, and do they carry?
You
Find the one risky place in the diff and check it.
Judgment · Blunder Check
Name one place where it could be wrong, then check it.
You
Approve.
You sign off here
Judgment
The countersignature. You countersign; you do not take the sign-off away from the author.
Author
Merges.
You
End of day.
Accountability · Post-Game Analysis
A short look back in the evening: what did I think through myself today?
A supplement to the main case: you countersign; you do not take the sign-off away from the author.