Commentary
Guided demo

From a review request to a human decision.

A launch team reads a rendered PR, questions the rollback plan, and asks an agent for a focused revision. Follow the decision from Inbox through verification.

Illustrative walkthrough: these examples do not create requests, run an agent, or record approvals. Open a real sample to explore the review workspace.

  • Rendered PR
  • Anchored feedback
  • Exact revision
  • Human approval

Keep each kind of evidence distinct.

A reply, a completed agent task, and an approval answer different questions. None silently substitutes for the others.

Illustrative revision status

  • Agent reportThe agent reports that it revised the rollback section. This is a fulfillment claim, not independent verification.
  • VerificationA reviewer inspects Changes and the check evidence against the acceptance criteria.
  • Human acceptanceAn authorized person accepts the exact revision through the existing approval path. A later revision needs its own assessment.

Four checkpoints make the loop reliable.

Each checkpoint answers a different question and leaves the final preference or approval decision with a person.

1. Critique before publishing.

Inspect repository and environmental evidence, then classify feedback as blocker, material risk, suggestion, question, or positive observation.

2. Open one durable artifact.

Choose CLI for a local file-backed review or MCP for an existing remote/provider-backed review. Combine them only for distinct operations.

3. Revise without erasing authorship.

Inspect thread authorship and gate state. Reply or revise when appropriate; do not resolve independently authored feedback prematurely.

4. Stop at the human gate.

The agent can report that evidence and acceptance criteria are satisfied. Only the existing human-controlled path approves downstream work.

Follow the launch review.

Six illustrative stages show how a bounded Inbox request becomes a careful review when the decision needs evidence.

  1. 01

    1. Receive the Inbox question

    The request names the sender, the launch decision, and the artifact to inspect. Reading it alone does not complete the task.

  2. 02

    2. Read the rendered PR

    Open the launch brief in Preview. Use Document or Changes independently from Preview or Raw.

  3. 03

    3. Anchor the feedback

    Attach the rollback-owner question to the affected section so the next revision has precise context.

  4. 04

    4. Ask for an agent revision

    A connected agent retrieves scoped feedback and revises the source. Its completion report remains a claim about work performed.

  5. 05

    5. Verify the change

    Read the exact comparison and check the rollback evidence. Resolving a conversation does not establish human sign-off.

  6. 06

    6. Make the human decision

    An authorized reviewer accepts or requests changes for the exact revision. Approval does not automatically merge, deploy, or verify external execution.

Try the loop with a real artifact.

Start with the sample, then install the review pack when you are ready to connect a local file or remote review.