Findings and Outcomes
Atlas Review is not just a pass/fail surface. The useful unit is the finding plus its current outcome.
Findings
Section titled “Findings”Review results should give you:
- a summary and verdict
- structured findings
- evidence or anchors that explain why the finding exists
In the desktop app, this usually appears as a review summary at the top and a finding list underneath it. The useful workflow is to move from verdict to specific evidence, not to treat the top-line status as enough on its own.
Outcomes
Section titled “Outcomes”A finding typically moves into one of these states:
- addressed
- dismissed
Use dismissal only when you have a real rationale, not just to clear noise.
Persisting the outcome matters because Atlas tracks that decision across reruns and publication flows.
Rerun Discipline
Section titled “Rerun Discipline”After code changes:
- rerun the review
- confirm the finding no longer reproduces
- verify the updated review snapshot reflects the current branch or PR state
Publication
Section titled “Publication”GitHub publication should happen only from review snapshots that are current and eligible for publication.