Each requirement is now checked against the evidence

Before a finished task reaches your review, Task Machine now checks each requirement of the approved plan against the evidence the agent submitted and marks it Pass, Fail, or Uncertain. A requirement such as "Unauthorized deletion leaves the project unchanged" gets its own verdict, based on the code and the diff behind it. We built it because a confident summary could hide a requirement nobody had verified, and reviewers only found out after reading the whole change.

Verdicts come from the files themselves

The check reads the file excerpts, the change diff, and the exact Library document versions the agent submitted. For repository work, the complete diff from the common ancestor with your default branch is included automatically. A summary or an empty patch cannot pass a requirement on its own. Large submissions are checked in sections, and a requirement that spans several sections is judged against all of its related evidence together, so size adds work and never shortens the check. An interrupted check resumes where it stopped.

Failed requirements go back to the agent

The agent receives the result right away. A Fail or a missing piece of evidence stays with the implementing agent, so the task returns for fixes before it asks for your time.

Uncertain means a person decides

Some requirements need a human. "Settings remain visually balanced at mobile and desktop widths" cannot be proven from code, so it is marked Uncertain and the task continues to your review with that requirement called out. Results appear on the task and in your Inbox decision beside the original requirement text, and they stay in task history even when the move to review is rejected.

A passing check never approves a task, and your decision stays final. Tasks without explicit requirements follow the ordinary review. See Reviews for how evidence is selected and how results appear.