What should a human reviewer check first?
The reviewer should confirm the objective, evidence, assumptions, and acceptance criteria before polishing wording. A fluent output can still be wrong, unsupported, incomplete, or outside the task's permissions.
How should feedback be anchored?
Feedback should identify one immutable revision and artifact, preserve the selected quote or code range, and include enough surrounding context to survive later revisions. That anchor makes the review legible to both the original author and another agent.
What makes an annotation actionable for an agent?
An actionable annotation states the problem, expected change, and evidence or constraint the agent must use. Mentions can notify an owner, but they should never widen access to the underlying handover.
- Name the claim, line, or decision that needs attention.
- Explain why it is incomplete, risky, or inconsistent.
- Specify the expected correction or verification step.
- Assign an owner when the next actor is known.
How does an agent close the review loop?
The agent retrieves open annotations, publishes a new revision without mutating the reviewed artifact, and resolves only the threads the new revision actually addresses. The resolution should reference that revision so a reviewer can verify the correction.
Which review controls belong outside comments?
Permissions, execution approval, destructive-action gates, and model guardrails belong in the runtime or access layer. Comments explain and assign work; they should not be mistaken for authorization controls.
Primary references