The latest file is not always the right file
With three report drafts and two implementation options, opening the newest one feels natural. But the last edit may have fixed a typo while dropping an important constraint. A version number cannot make an acceptance decision for you.
When two AIs edit the same document in turn, comparison gets harder unless you know which version each tool used as its starting point.
Make a separate decision for each version
Do not carry an accepted status automatically into a new version. Even if the old one passed, check the changed area and its connected flow again. A useful note says 'title fits on a phone' rather than simply 'looks good.'
- Needs review: not yet compared with the original request
- Changes requested: record the blocking issue and how to reproduce it
- Accepted for use: note what you checked and any remaining risk
Keep review state with the artifact
Wellnote separates review notes and status by artifact version. Keeping accepted and changes-requested versions together helps the next session avoid adopting the newest file by default.