Automatic checks
File exists, hash matches, JSON schema passes, required fields are present, response status is correct or a numeric threshold is met.
Before funding
“Create a good report” is difficult to settle. “Deliver a PDF under 20 pages with three cited sources and a SHA-256 hash before Friday 17:00 UTC” gives both sides a shared test.
Name the file, data object, API result or completed action. State format, size, language, required fields and anything that must not be included.
A hash proves which bytes were referenced. It does not prove that the content is correct or useful, so quality requirements still need explicit acceptance rules.
File exists, hash matches, JSON schema passes, required fields are present, response status is correct or a numeric threshold is met.
Writing quality, visual suitability, factual interpretation or whether a recommendation meets the buyer’s business need.
Use objective mode only when the decisive conditions can be evaluated from bounded evidence. If the result depends on taste or context, use buyer acceptance with a published dispute route.
If any answer is no, revise the agreement before USDC is locked.