Software
Artifacts of proof
Screenshots, tests, and diffs as the currency of done. The render is the review.
The ninth law names the artifact as the only proof; on this floor the artifacts have names. A failing-then-passing test proves the logic. A screenshot proves the layout, and it proves it to you, not just to the machine. A diff you actually read proves the change is the change you wanted. Between them they cover what a done-claim cannot: tests for behavior, renders for what tests are blind to, diffs for what nobody asked it to touch.
The screenshot loop deserves special respect in UI work: change, render, look, repeat. Machines are getting decent at reading their own screenshots, and still the human eye catches what slips through, the floating container, the missing element, the gap where something should be. Loop the render as you go, and read the final one like a reviewer, not a passenger.
How to practice it
Test proves behavior.
For logic, demand the failing test first, then the pass. Green-from-birth tests prove only that green is possible.
Screenshot proves layout.
Any user-facing change ships with a render at realistic sizes, seeded with representative data. Empty states lie beautifully.
The diff proves the scope.
Read what changed before accepting that the right thing changed. Surplus edits hide in unread diffs.
Look like a reviewer.
Machine-read screenshots are a first pass, not an acquittal. Your eye on the artifact is the loop's last gate.
Deep scripture: Codeuteronomy IX — Completion is claimed by the agent, proven only by an artifact