Review the actual deliverable
Open the reported artifact in its source system. Compare it with the task brief, check supporting evidence, and confirm the output is usable before accepting the outcome.
03 / REVIEW
Completion deserves a second question.
Keep agent-reported success separate from human acceptance with an explicit outcome review record.
WHY IT MATTERS
Finished and accepted are different states.
A run can finish successfully and still produce an incomplete report, an irrelevant summary, or a result that needs correction. Make the quality decision visible.
RUN HISTORY
Weekly research brief
Reported complete- Collect sources
- Reported
- Draft the brief
- Reported
- Human outcome review
- Awaiting review
An agent reports completion. Your team decides whether the result meets the brief.
Record a human decision
Accept or reject the reported outcome with review context. Keep the agent’s completion claim and the reviewer’s judgement distinct so neither is mistaken for the other.
Use rejected work to improve the next run
Look for repeated missing sources, formatting problems, or unsupported conclusions. Feed those specific observations back into the workflow you own.
START WITH ONE WORKFLOW
Put your next run
under supervision.
Connect the agent you already run. Build confidence from the work you can actually review.