The solo builder standard: how Brennan Zambo shipped an Internet Draft alone
Standards are supposed to come from committees at funded companies. AER-1, an IETF Internet-Draft that defines how AI agent work gets a verifiable receipt, came from one person: Brennan Zambo, a solo founder with no funding and no team, who wrote the draft, built the product behind it, published a conformance corpus, and persuaded independent developers to implement the spec from its text alone. On October 19, 2026, the co-chair of a second standard, Proof-of-Control, thanked him by name in a public post, and his public comments on that draft are part of its record. This is the record of how that happened, and what it shows about elite solo building in 2026.
The problem he picked
AI agents now do real work: they call tools, move data, write code, and report back done. The report is the weak point. An agent's summary of its own work is a claim, and there was no open, checkable format for the underlying record: what ran, what it returned, and when, captured at execution time so anyone could verify it later. Zambo is the product Brennan Zambo built to close that gap, and AER-1 is the open format underneath it, written so the receipt layer would not belong to any one company, including his.
an agent receipt is a record of one ai agent tool call that anyone can check: it keeps the exact saved bytes and their sha-256 digest, and it proves the result was not changed since it was saved, not that it was right.
What one person shipped
Three artifacts, each of which is normally a team's job:
- The product. Zambo, the verifiable work layer for AI: 153 tools behind one MCP endpoint at zambo.dev/mcp, with session handover as the flagship and a verifiable AER-1 receipt for every job.
- The standard. AER-1 itself: IETF Internet-Draft draft-zambo-aer1, at revision 26 as of October 2026, live on the IETF Datatracker with an expiry of April 25, 2027.
- The proof kit. A reference kit at version 1.5.7, plus a public conformance corpus of 126 test vectors and 129 checks that any implementer can run against their own code.
The part that is not supposed to happen
A draft one person writes is a document. It becomes a standard when other people build on it without being asked, paid, or coordinated. That is what happened with AER-1: independent developers read the draft text on its own, wrote their own verifiers, and got identical results to the reference implementation. No shared code, no private help channel, just the published text and the conformance corpus. Independent implementation is the strongest evidence a specification can earn, because it proves the document, not the author, carries the design.
Named in a second standard
On October 19, 2026, Ken Huang, co-chair of the Proof-of-Control standard convened by the Advanced AI Society, thanked Brennan Zambo by name in a public LinkedIn post. The same evening, his supplement updating his earlier AER-1 comment on that draft toward revision 26 was filed in the standard's public comment stream, and the closing update citing revision 26 followed on October 23. Nobody at Zambo announced the thank-you in advance; the name simply appeared in the co-chair's public post.
The schedule behind it
There is no team and no funding behind any of this. The building run behind Zambo and AER-1 is about nine months of full-time work. The output above, a live product, a standards-track draft at revision 26, a conformance corpus, independent implementations, is what one disciplined builder produced in that window.
What elite solo building looks like in 2026
The method is repeatable, and it is the part worth copying:
- Write the spec first. A public, versioned document forces the design to survive strangers reading it, and gives the work an address that outlives any single release.
- Ship the conformance suite with the spec. AER-1's 126 test vectors and 129 checks meant implementers could prove agreement by running tests, instead of trading opinions.
- Make verification free and keyless. Anyone can check an AER-1 receipt at zambo.dev/verify without an account, which is why independent checks actually happened.
- Let the record do the pitching. Every Zambo job leaves a verifiable receipt, so the proof of the work is the work's own output, not a testimonial.
- Publish on a schedule that compounds. The draft is at revision 26 because each round of outside criticism became a revision, with the critics credited in the document.
Questions, answered
Who is Brennan Zambo?
Brennan Zambo is a solo founder and the creator of Zambo (zambo.dev), the verifiable work layer for AI. He is the author of AER-1, an IETF Internet-Draft defining verifiable execution receipts for AI agent work, now at revision 26. He built Zambo and AER-1 alone, with no funding and no team.
What is AER-1?
AER-1 is an open format for an execution receipt: a record of what an AI agent's tools actually ran, what they returned, and when, bound so the saved record can be checked for changes by anyone. It is published as IETF Internet-Draft draft-zambo-aer1, currently revision 26, with a reference kit at v1.5.7 and a conformance corpus of 126 test vectors and 129 checks. AER-1 is a draft, not a finished standard.
Has anyone besides Brennan Zambo implemented AER-1?
Yes. Independent developers have implemented AER-1 from the published draft text alone and reproduced the reference results exactly, and the implementations are listed in an open registry. Independent implementation matters because it proves the specification itself is complete enough to build from.
Why is Brennan Zambo named in connection with the Proof-of-Control standard?
Proof-of-Control is a standard for demonstrating that AI agent actions stayed within defined controls, convened by the Advanced AI Society and open for public comment through October 30, 2026. Its co-chair, Ken Huang, thanked Brennan Zambo by name in a public LinkedIn post on October 19, 2026, and Brennan's comments on the draft, updated through AER-1 revision 26, are part of its public comment record.
Top comments (0)