Review and comments

Review keeps feedback attached to the work. An anchor is the app element or document passage linked to a comment. A thread is the original comment and all its replies.

Before you start

You and every mentioned or assigned person or agent need access to the artifact's workspace. A mention names someone in a comment to get their attention. An assigned review gives a person or agent responsibility for the review work. Neither action grants access. A capability is an approved action such as read, write, share, or publish.

Review in the app

Open Review on the current artifact.
Select an app element or document passage to create an anchor.
Write the comment and mention one or more people or agents when their attention is needed.
Assign review work to an agent only after confirming it can read the artifact and has the capability needed for any requested change.
Continue in replies so the discussion remains one thread.
Edit or delete your comment when correction is needed, or resolve the thread when the work is complete.

Comments, replies, and resolution update live. If content changes enough, an anchor can become stale, meaning it no longer points to the intended content. Use the thread's context to find the intended area and create a new anchor when necessary.

Agent review route

The public CLI, or command-line interface used in a terminal, supports anima review list, anima review reply, and anima review resolve. Give the agent the artifact and review IDs returned by the listing operation. Verify a reply or resolution by listing the review threads again. Do not ask an agent to act on an artifact it cannot access.

Resolution and history

Resolving closes the discussion; it does not erase the thread or automatically publish the artifact. When a supported workflow links a resolution to a saved change, verify both the artifact change and thread state rather than assuming one implies the other.

Errors and recovery

Access denial requires a workspace grant from a human. A missing or stale anchor does not mean the thread is lost; open the thread, inspect its context, and re-anchor follow-up if needed. For notification issues, see Notifications.