Review agent work
Inspect workflow evidence and approve individual page proposals.
Each workflow run records its status, workflow version, evidence, and page proposals. Open the run from the workflow's run history.
Inspect the evidence
Review the architecture-change decision and its rationale. Follow the cited repository files and documentation pages to check the context used by the agent.
When a run proposes a C4 diagram, review the Mermaid content alongside the documentation changes. A successful analysis does not automatically mean that every proposal should be accepted.
Approve or reject a proposal
Proposals can create a page or update an existing one. Review them individually, then approve or reject each page proposal.
Approval allows that proposal to be applied to Notion. Rejection keeps it from being applied. Mixed decisions can leave a run partially applied.
Understand run states
| State | What is happening |
|---|---|
| Queued | The run is waiting to be processed |
| Analyzing | Adria is evaluating the change and preparing proposals |
| Awaiting approval | Proposals are ready for review |
| Applying | Approved proposals are being written |
| Succeeded | The run finished successfully |
| Partially applied | Only part of the proposed work was applied |
| Failed or interrupted | The run did not finish normally |
Handle conflicts
An update proposal records the Notion revision it was based on. If the page changes before application, a conflict can prevent the stale proposal from overwriting newer content.
Review the current page and the proposed changes before retrying. Use the dashboard's retry controls for failed runs or failed application attempts.
Keep a record
Run history links outcomes to the workflow version and originating change. When behavior needs adjusting, edit the workflow's instructions or scope, preview the new version, and review later runs against that definition.