human-acceptance / 90-second captioned walkthrough
No audio. Explanations of saved evidence; not a new live client-session capture.

00:00:00.000 – 00:00:15.000
OrgX / completion and acceptance

Actual local run: human acceptance pending
Synthetic rejection: teaching example only
No customer or real reviewer is simulated
This package separates a real local run from an explicitly synthetic review example.

00:00:15.000 – 00:00:30.000
Three states answer different questions

Agent completion: did the producer finish?
Conformance: does the record validate?
Human acceptance: what did the person rule?
Producer completion, record conformance and human acceptance are separate facts.

00:00:30.000 – 00:00:45.000
The actual run has no human ruling

receipt.json
  outcome.status: succeeded
  verification.status: passed
  outcome.acceptance.status: pending
The actual local receipt records completion and passing checks. It does not invent a human ruling.

00:00:45.000 – 00:01:00.000
A valid record can carry a rejection

synthetic-rejected-receipt.json
  evidence class: synthetic_example
  conformance: valid
  acceptance: rejected
The synthetic example remains conforming while it records rejection. This demonstrates the format, not an authenticated human decision.

00:01:00.000 – 00:01:15.000
Review the work itself

1. Confirm the criteria and artifact version.
2. Inspect evidence, failures and unknowns.
3. Establish reviewer identity and authority.
4. Record the actual ruling separately.
Before acceptance, inspect the requested criteria, exact artifact and evidence, then establish the actual reviewer and their authority.

00:01:15.000 – 00:01:30.000
Keep producer claims in scope

A producer-supplied acceptance field
is not an authenticated human ruling.

Validate your receipt at
useorgx.com/agent-work-receipts
A producer field cannot authenticate a reviewer. Validate the record, then use an authorized review system for the person’s decision.