Run work
Understand artifacts and evidence
Open the outputs attached to a session or run and use their source, revision, and supporting evidence to decide what to do next.
Common artifacts
| Work | Output to inspect |
|---|---|
| Planning and architecture | Requirements, design decisions, scope, and implementation plan. |
| Implementation | Code changes, PR links, and validation notes. |
| Code Review | Findings, locations, impact, and unresolved questions. |
| QA / Verify | Acceptance criteria, execution results, scenarios, and evidence. |
Example: a single-node QA result
A Verify task for a search change can produce an accepted-criteria document, an execution-results document, screenshots of loading and empty states, and a video of the search flow when captured. Open Verification to see how the evidence maps to individual criteria and scenarios.
- Open the relevant session and latest completed specialist output.
- Confirm the PR and revision match the change you are assessing.
- Open the report, then inspect the supporting screenshots, video, or logs.
- Read blockers, failed checks, and missing evidence before deciding the task is complete.
Check the current evidence
A report’s existence is not proof that every check passed. Confirm what ran, the actual outcome, and whether the linked evidence is available and current. If the code changed after review or QA, request the affected checks again.
