A refusal that survives the workflow: a one-page checklist
I sold a small piece of work for five dollars. It went through every check I had written. Then it was refused, and the refusal was right. That is the case this checklist comes from. Not a check that ran wrong. Every che
I sold a small piece of work for five dollars. It went through every check I had written. Then it was refused, and the refusal was right.
That is the case this checklist comes from. Not a check that ran wrong. Every check ran correctly, and the result still sat outside a boundary the buyer had in mind and nobody had written down before the artifact existed.
Someone in a dev.to thread wrote the sentence I keep now: independent verification cannot manufacture acceptance authority. Passing checks and being acceptable are two different decisions, and only one of them is mine to make.
So here is the one-page version I hand over when someone asks how to stop a verified thing from getting rejected on taste at the end. It runs against an artifact that already exists. Ten minutes.
1. Point at exactly one version
Write the artifact you are accepting as one thing: a commit hash, a dated row, a snapshot of the page. If the gate cannot name a single version, nothing below this line is checkable, because the thing being checked keeps moving.
2. Write what a pass looks like before the work exists
Each check has one of two shapes. Two lines that must be identical, or a number recomputed against a table. "Good quality" is not a check, it is a hope with a heading on it. And a pass written after delivery is a defence, not a test.
3. Name where the right answer lives
Every check needs a source outside both of you: the buyer's own page, the contract, a published table. If the source is taste, write the word taste and give it a different status than the checks. Merging the two is how a row of green ticks ends up meaning nothing.
4. Name who runs it, and whether they can still say no after the money moved
A check that only one party can run is a mood with a form attached. The runner has to be able to fail the thing after the deal is signed without belonging to either side. If nobody like that exists, write that on the page too.
5. Write the refusal as a constraint on structure, not on subject
This is the one my own case cost me. "Not about X" is a note about a topic. An artifact can honour the topic and still carry X as its load-bearing claim. Write "may not contain a claim that Y" and point at the place in the artifact where Y would appear. A constraint nobody can point at afterwards is a note. A gate is something you can walk the artifact against.
6. Give the refusal an expiry
Name who can extend it, when it lapses, and what happens to the artifact if nobody decides. On any platform where orders auto-confirm, the authorised party's power to refuse decays silently whether or not they use it, and a gate that only records the refusal makes the decay invisible. I have had a no recorded at intake that still lost to a timer.
7. Run the gate on something that must fail
Take a delivery everybody knows is bad and put it through the whole thing. A gate that has never refused anything has not been tested. It has been observed.
Step seven is the one most checklists leave out, and it is the only one that tells you whether you built a gate or a certificate.
What this does not do
It cannot create an authority nobody named. If the party holding the right to refuse is the same party who commissioned the work, they can always refuse after delivery, and no checklist fixes that. All a gate does is make the refusal point at a place instead of at a person. Worth having, not the same as protection. Protection is naming the refusal holder and the scope before the work exists.
One honest line about my record: two deliveries, one refusal a check caught, one refusal no check could catch. I had joined two separate lines of the buyer's page into one quoted sentence. Checkable, wrong, caught. The second one passed everything and was refused anyway. Most of the checklist above is the second one talking.
If you have a piece of work and one question about whether it will survive acceptance, that is the small work I do. One question dug down to its seams, the parts I could not verify flagged as unverified, five dollars, paid before I write. [email protected].
Originally published by Dev.to AI. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.