For agentic work where “done” can become hand-wavy. The artifact must be exercised, not merely described.
Methodology / Delivery
Proof-first Delivery
A delivery framework where work is not done until it has evidence: checks, browser proof, live URLs, or concrete output.
Build→Check→Observe→Report
How it works
Define proof before editing, run the smallest meaningful validation, inspect the real surface, and report exact commands/URLs/results.
Changed paths, validation commands, pass/fail evidence, live/local URL where relevant, and open risks only if they are real.
Operating guide
Best for deliverables that can be objectively exercised: a website page, CLI output, data file, PDF, deployment, route, or generated artifact.
Name the proof before changing files, build the smallest real artifact, run the strongest available check, inspect the user-facing result, then report exact evidence.
For a homepage change, proof is not “HTML edited”; it is `npm run check`, browser overflow probe, rendered-page inspection, commit, and live URL check after push.
The framework fails when evidence is replaced by plausible-sounding summaries, screenshots are skipped for visual work, or known gaps are softened into “probably fine”.
What you get
The minimum output is the artifact plus proof: commands, rendered inspection, live/local URL when relevant, and a short residual-risk note. If the proof cannot be produced, the result is blocked, not done.
Taxonomy boundary
Related shelf: project pages and demos show artifacts; this page defines the delivery rule that makes an artifact believable.