Proof Room
Every deliverable ships with a receipt.
the receipt is the record of what was asked, what was checked, what passed, and who accepted it. This one is illustrative — the method, not a client.
The task.
Task Specification
# OBJECTIVE — what “done” means, agreed up front objective: rewrite 40 product blurbs in brand voice protected: [prices, SKUs, model names, claims] constraints: no new claims · ≤ 40 words · US spelling verify: diff vs source · claim-check · read-grade accept_when: all checks pass and owner signs
The checks.
- PASSProtected values unchanged (prices, SKUs)0.4s
- PASSNo unsupported claims introduced0.6s
- PASSLength & spelling within spec0.3s
- HOLD2 blurbs drifted off brand voice → returned0.5s
- WAITOwner acceptance required to publish—
38 / 40 accepted
nothing ships until you sign
What a receipt proves.
- the objective existed before the work;
- protected values were listed and defended;
- every check ran without a human in the loop;
- failures were returned, not hidden;
- acceptance is a signature, not a vibe.