"Done" means evidence
An agent saying "done" is a claim. It counts when there is evidence of it, tied to the exact code revision.
At Blume, we treat “done” as a claim. You can rely on it when there is evidence for it, and when that evidence is about the code you are about to ship, not an earlier version of it.
What goes wrong without it
Done as a claim
An agent writes: “Sign-in works. I tested it and all tests pass.”
What was tested? Maybe only the unit tests. What was seen? Nothing you can look at. Which code? The agent changed two files after the run. So you start the app yourself, restart it, and you are logged out.
Done with evidence
The plan says what proves the outcome: “A signed-in person is still signed in after the app restarts”, checked end to end.
The agent runs that check against commit 1a2b3c4 and registers the steps, a screenshot of each, the outcome and the commit. If the code changes afterwards, the check is no longer met until it runs again.


What to do
- A claim names its proof: an end-to-end run, a unit or integration test, a manual check with notes, a screenshot.
- Evidence names its revision. A result without a commit proves nothing about the code in front of you.
- New code needs new evidence. Rerun the checks after the last change, not before it.
- Keep failures. A failed run shows what the fix had to solve.
In Blume
- Agents register results as evidence with their type, outcome and commit.
- An acceptance check is met when evidence of its type passed at the current code. Older evidence is marked as such.
- New code, newly opened work or a failing check withdraws an approval. See reviews and tests.