delivery-prooflisted

# Delivery Proof Completion is a claim backed by evidence, not a synonym for code written, tests run, or a ticket closed. Apply this contract whenever another skill defines acceptance criteria or reports progress. ## Preserve the artifact chain Trace every desired outcome through the artifacts that are meant to deliver it: `outcome -> decision/spec criterion -> implementation ticket -> change -> proof receipt` Record delivery obligations as stable `OBL-*` identifiers. Every obligation needs an owner or next artifact and a discharge condition. An artifact may finish its own job while carrying obligations forward; an effort is complete only when every effort-level obligation is discharged. ## Name the required proof level For each criterion, report the highest level the evidence actually establishes—never a higher one. The overall state is bounded by every unmet required criterion, not by the best result in the set: 1. **implemented** — the intended change exists in the reviewed change set. 2. **locally-verified** — independent checks pass in a representative local or test environment. 3. **deployed-verified** — the deployed target environment passes the required checks. 4. **outcome-verified** — the real user/business outcome is observed over the required population or journey. A lower level never implies a higher one. A commit proves only that a checkpoint exists. A unit test cannot prove deployment, and a successful deployment cannot by itself prove the outcome. Ch