Review AI proposals

AI can propose memory changes, tickets, roadmap updates, duplicate resolutions, doc updates, and chat pending actions. Review turns generated output into trusted workspace state.

Find pending review items

1. Open Today to see review pressure.
2. Open Inbox for proposed changes.
3. Check the project picker.
4. Use All Projects for organisation-wide review.
5. Use a specific project for project-scoped review.
6. Wait for AI status to finish if you expect new items after a chat, doc edit, project Check-In, or conflict scan.

Agent Runs can finish after the page that started them has already returned.

Review a memory diff

1. Open the Inbox item or Memory Diffs.
2. Read the proposed fact.
3. Open the source record.
4. Check whether the fact is true today.
5. Check whether it belongs in organisation memory or project memory.
6. Check whether the wording is durable and specific.
7. Accept accurate facts.
8. Reject guesses, stale claims, duplicates, or facts in the wrong scope.

Memory should be a trusted fact layer, not a transcript of every generated suggestion.

Review an operating proposal

1. Open the proposal in Inbox.
2. Read the target, summary, and rationale.
3. Open related tickets, docs, risks, or roadmap records.
4. Confirm the proposed change is still needed.
5. Accept the proposal if it should affect workspace state.
6. Reject it if it is wrong, stale, speculative, duplicated, or scoped incorrectly.
7. Recheck the affected area after the action completes.

Review a chat pending action

1. Read the chat answer around the action.
2. Confirm source groups and references were appropriate.
3. Confirm the target item and active project.
4. Apply the action.
5. Open the updated or created item.
6. Edit the result if needed.
7. Add a human comment when the rationale should be visible outside Chat.

Chat pending actions may not create a separate Inbox item because you confirm them inside the conversation.

Review a generated doc or ticket

1. Open the generated item.
2. Check title, scope, references, and owner.
3. Fix vague claims or missing acceptance criteria.
4. Add labels, custom fields, parent, due date, or assignee.
5. Confirm board visibility or docs tree location.
6. Extract memory only after the source content is reviewed.

AI drafts can be useful starting points, but people own the final workspace record.

Review duplicate ticket proposals

1. Open Tickets.
2. Select Scan conflicts or open the Inbox duplicate proposal.
3. Compare the recommended keep and archive tickets.
4. Open both tickets if the summary is not enough.
5. Keep the ticket with the clearest history, references, comments, and current owner.
6. Accept the proposal if one ticket should be archived.
7. Reject it if both tickets should remain active.

Rejecting a duplicate proposal is often correct when tickets look similar but represent different work.

Verify after acceptance

1. Refresh the affected page.
2. Check the item status changed from pending to accepted or rejected.
3. Open the updated ticket, doc, memory item, roadmap item, or snapshot.
4. Confirm the activity or revision history explains the change.
5. Search for the related reference if the change should now be discoverable.

Related concepts: Inbox, Agent Run status, Memory diffs, Use AI Chat.