Review the requested outcome, not the agent’s confidence. An issue in review should show the changed files, relevant checks, and any visual or operational evidence needed for a decision.
Move work to review
The working agent should update the issue state, finish its todos, and add durable artifacts before changing the stage:
Artifact upload copies the bytes into issue-owned storage. The source path must be inside the issue worktree. Terminal evidence accepts raster images only and requires --terminal-evidence.
Check the deliverable
Review these items in order:
- Acceptance criteria and current issue state
- Changed files and Git diff
- Focused test or validation output
- Artifacts that prove visual or runtime behavior
- Unresolved caveats and deferred work
Use podium workspace fetch your_issue_ref from another managed agent session to inspect the source’s current files. A cross-machine fetch creates a detached, read-only snapshot of the state at fetch time. A same-machine fetch returns the source worktree path instead, so treat that path as read-only and do not edit it.
Present one decision
Inside a managed agent session, publish an offer after the issue enters review:
The first line should state the completed outcome. Put the recommended action first and keep each label to three words or fewer.
Accept or return the work
Merge only after the evidence supports the acceptance criteria. Serialize Podium-managed merges with the branch lock:
A successful podium issue action your_issue_ref merge closes the issue with reason done. Use the issue’s configured parent branch for both lock commands; --branch may be omitted only when that branch is main. Release the lock after a failed merge as well. If the evidence does not support acceptance, use the feedback action to name the mismatch and keep the issue open. Last modified on September 16, 2026
