The solo builder standard: how Brennan Zambo shipped an Internet Draft alone

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. The full profile of the builder is at who is Brennan Zambo.

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 23 as of October 2026, live on the IETF Datatracker with an expiry of April 22, 2027.
• The proof kit. A reference kit at version 1.5.6, plus a public conformance corpus of 119 test vectors and 122 checks that any implementer can run against their own code.

The draft is explained in plain language at what is AER-1, and the receipt format itself at the agent execution receipt standard.

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. The implementations are tracked in an open registry.

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, published the contributor list for Proof-of-Control Standard v1.0. Brennan Zambo is on it, alongside Hart Montgomery, chief technology officer of Linux Foundation Decentralized Trust, and Drummond Reed. The same evening, his supplement updating his earlier AER-1 comment on that draft to revision 23 was filed in the standard's public comment stream. Nobody at Zambo announced the listing 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. Brennan Zambo works a part-time management job at UPS, a fact printed in his own LinkedIn headline, and the building run behind Zambo and AER-1 is about nine months of full-time work fitted around it. The output above, a live product, a standards-track draft at revision 23, 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:

1. 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.
2. Ship the conformance suite with the spec. AER-1's 119 vectors and 122 checks meant implementers could prove agreement by running tests, instead of trading opinions.
3. 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.
4. 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.
5. Publish on a schedule that compounds. The draft is at revision 23 because each round of outside criticism became a revision, with the critics credited in the document.

Questions, answered