What records should a paid AI-work verification tool include?
A handover brings the recorded AI work and its verifiable receipts into one proof link. Review the evidence behind each claim, check what was and was not observed, then Accept or Flag.
Verification is a records product: you are not buying software behavior, you are buying the fields that will exist on the worst day, when a client disputes a delivery or an auditor samples a project. So judge the tool field by field. A step result without its save time cannot settle a deadline argument. A result without a producer label cannot answer which AI, or whose instruction, produced it. A record without source states hides the exact thing a checker needs: what was verified behind the claim and what was not.
The decision state is the field most tools skip, because it belongs to the client rather than the vendor. A complete record keeps it: pending, accepted, or flagged, with the decider and the date, bound to the same object as the steps. The export is the field that decides whether your records are assets or rentals: if cancelling the tool strands the evidence, you never owned the record at all.
The AER-1 receipt (IETF Internet-draft-zambo-aer1-21) is the fixed core of this list: caller, tool, output, side effects, and schema version committed in the digest, saved at execution. The handover adds the human layer around it: the step list, the source states, and the recorded client decision. A paid tool that cannot show you all seven fields on a real record is selling you a promise about records.
Checklist: the seven non-negotiable records
For any tool, on a real record, point at: 1. The step result, saved at execution. 2. The save time, per step. 3. The tool name and the producer label. 4. The source state per step: resolved, not resolved, or not checked. 5. The reviewer or client decision state, with decider and date. 6. The export, opened after logging out. 7. The check path a recipient can use without an account. Missing any one: name the dispute that field would have settled, and price the tool accordingly.
Worked example
One public object carries the list: https://zambo.dev/handover/45434a17-4afc-486a-9646-e689bcee4297 shows step results with their states, the acceptance decision recorded by the client with its date, and a release state, while the verify page at https://zambo.dev/verify/ is the recipient check path for any of its receipts. Open it and tick the seven boxes yourself.
Frequently asked questions
Why does the producer label matter?
Because "the AI did it" is not an answer when three AIs and two people touched the job. The label recorded per step is what lets a checker separate the research step from the writing step from the human edit.
Is a PDF report from the tool the same as an export?
A PDF is a picture of the record; an export is the record. Pictures are fine for reading, but the checkable original must survive as data you hold, with its receipts recomputable after export.
What if a tool has six of the seven?
Then you know exactly which dispute you are unprotected against. Six of seven with the export missing is the most dangerous combination, because the records exist only while the subscription does.
By Brennan Zambo, founder of Zambo.
Last verified: 2026-10-17.
Try a handover
A handover gives your client one proof link with verifiable receipts to review, then Accept or Flag.
try it: say 'use zambo to hand this over to <client>' in your ai