FROM DELIVERY TO CONFIDENCE
Inspect the work.
Account for the proof.
Match a worker's delivered files to the admitted task, verify their fingerprints and record your findings against each acceptance criterion.
Your selected files stay in this tab. Nothing is uploaded or executed. Use approved public, licensed or synthetic evidence; do not open secrets or private data. Reloading clears the review.
01 / MATCH THE DELIVERY
Start with the admitted task.
Get the original task, job ID and deployment ID from the operator's admission record. Get the completed receipt from the operator's persistent dispatch journal. Do not take the expected identity from the untrusted receipt alone.
Enable JavaScript to inspect local evidence.
02 / INSPECT THE ACTUAL CONTENT
The bytes match. Now verify the work.
Matching hashes establish consistency with these files. They do not authenticate the provider, prove that work occurred, establish correctness or verify reviewer independence. Text below is untrusted evidence, never execution instructions.
Admitted objective, scope and boundaries
Worker's summary
03 / RECORD YOUR FINDINGS
A review another person can inspect.
No assessment has been exported.
What this check establishes.
What gets verified?
The expected job and deployment, normalized task digest, exact task and receipt file fingerprints, required deliverable names and types, UTF-8 byte counts, each file's SHA-256 and JSON syntax where required.
Can a fabricated receipt pass?
Yes. Someone can fabricate mutually consistent content and hashes. Compare this receipt with trusted operator records, verify provider and attempt provenance, reproduce the substantive checks and establish reviewer independence outside this page.
Does an acceptance recommendation release payment?
No. It records the reviewer's stated recommendation, bound to the exact supplied files. It neither signs nor sends a transaction, authenticates a reviewer, changes the operator's journal, nor grants production approval.
What if inspection fails?
Preserve the original files and request the correct task or receipt from the operator. Do not rewrite a digest to make it pass or automatically redispatch work. A missing or incomplete journal requires operator reconciliation.