Use no-work when the responsible choice is to stop
A no-work outcome names what was inspected and why the requested addition should not proceed.
In the fixed workshop job, the source contains no price. If the task asks to add a price without another source, that requested addition ends with no work and an explicit unknown. The rest of the supported brief does not need an invented number.
Use failure when the job could not complete
A failure record names the stage reached, last intact artifact, failed action, and safe next attempt. It does not imply that the content itself was wrong.
The canonical demonstration completes, so it supplies no failure event. A failure example would invent a second history and does not belong in this article.
Use complete only when the declared job is complete
The fixed demonstration completes after review removes “Saturday sessions are available,” the corrected brief retains only confirmed details, and the checkpoint records schedule and price as unknown.
The labels describe work state, not quality theater. A complete artifact may contain known limits, and a no-work result may be the correct response to one unsupported addition.
Record enough to resume accurately
Keep the outcome beside the task boundary and latest intact artifact. Name the sources checked, requested change, stopping reason, and next question or repair. A later reader can then resume without treating a missing answer as a finished result.