Review the assistant’s work
Check the inputs, proposed actions, and evidence behind a conclusion.
The assistant can read context, edit working files, prepare saved records, and open affected work. Review the action at the point where it changes your Project or starts execution.
Check a proposed plan
Confirm its question, product version, Dataset and Model versions, requirements, criteria, and assumptions. Ask for source references when standards or outside documents influenced the plan. A question requesting information is not an execution approval.
Follow active work
The composer offers Stop while work runs. A draft can be queued with Queue next message; Send now steers active work. Stopping pauses the remaining queue. File edits offer diffs and guarded Undo.
Keep three decisions distinct
- Execution approval permits the reviewed work to run.
- Evidence review records what a result or submission establishes for a requirement.
- An Assessment decision approves, conditionally approves, or rejects a stated use.
A completed Run or generated report supplies evidence for review. Keep the human conclusion and Assessment decision explicit.
Use Activity to find work that needs attention outside the current chat.