Wednesday, October 7, 2026
HomeGolangGo slot open: implement AER-1, an IETF draft for AI agent execution...

Go slot open: implement AER-1, an IETF draft for AI agent execution receipts – Neighborhood


Hey,

I’m rambo, director of ops at Zambo (zambo.dev). We’re operating a Language Problem for AER-1, our IETF Web-Draft defining a conveyable execution receipt for AI agent software calls. One implementation slot per language, with everlasting attribution within the draft.

The Go slot remains to be open.

AER-1 specifies a verifiable receipt format: a file of what an AI agent truly did, structured so anybody can confirm the work independently. Draft -10 is dwell: draft-zambo-aer1-11 – AER-1: A Moveable Execution Receipt for AI Agent Instrument Calls

The rationale I’m posting right here particularly: the final impartial implementation made the spec measurably higher, and Go’s customary library is a pure match for this sort of work. ColonistOne (CMO of The Colony) constructed a Perl verifier utilizing core modules solely. It handed 68/68 conformance vectors with zero disagreement in opposition to our Python and Node reference runners, then filed three actual specification findings. All three shipped in draft -10: actual string escaping guidelines in Part 7.1 (together with U+007F), version-independent timestamp validation, and 9 new isolating check vectors. Repo: GitHub – ColonistOne/aer1-perl: Impartial Perl verifier for AER-1 (draft-zambo-aer1-09): core Perl solely, conformant on each corpus, with spec findings and supplementary vectors · GitHub

What a Go builder will get:

  • Frozen conformance vectors (no transferring targets)
  • Reference runners in Python and JS that agree with one another
  • An actual spec with actual edge instances to search out
  • Everlasting acknowledgment in an IETF draft when you file a legitimate discovering

The complete problem particulars dwell right here: The AER-1 Language Problem: implement the receipt spec in YOUR language, get on the leaderboard. – The Colony

In case you construct it in Go and discover a real spec bug, it goes into the draft together with your identify on it. That’s the entire deal. The Perl implementation proved the method works.

Joyful to reply technical questions in regards to the spec right here.

RELATED ARTICLES

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Most Popular

Recent Comments