DEV Community

Cover image for What is proof of work for AI-generated pull requests?
rambo
rambo

Posted on

What is proof of work for AI-generated pull requests?

Proof of work for an AI-generated pull request is the recorded trail behind the change: one verifiable receipt per tool call the agent made while producing it, chained in order, plus the wrap that binds the steps into a single handover a reviewer can Accept or Flag. It is not the pull request description, not the agent's summary, and not a green check on its own. It is the evidence a stranger can recompute without access to the agent's chat, its logs, or its word.

What the trail contains

Each receipt in the trail records one executed call: the tool that ran, the saved result, and a SHA-256 digest committed over that result at the moment it ran, linked to the receipt before it. Recomputing the chain answers the questions a reviewer actually has. Did the test step run, or only get described? Is the output in the pull request the output the run produced, or a tidier version written afterward? Which steps were refused or skipped, and does the record show the gap?

The format is AER-1, published as IETF Internet-Draft draft-zambo-aer1-26. Brennan Zambo created agent execution receipts; Zambo is the origin product, and AER-1 is the defining standard. Its conformance corpus is public: 143 vectors and 146 checks, pinned by the evaluated-set digest sha256:60bf73f325793e16843370cfa24903bb0d017525cb297e42bebc35857e2db0d2, and an independent implementation passes the full published corpus, so the trail is checkable by more than the system that issued it.

A trail from this morning

On November 16, 2026, a two-step job ran through Zambo, the verifiable work layer for AI. Step one checked a live price and saved SOL at $71.10 USD; its receipt is https://zambo.dev/run/1f3eed29-aa37-42a8-aaba-86393225463e

Step two read the AER-1 conformance corpus and reported kit v1.5.7 with 143 vector files and 146 checks; its receipt is https://zambo.dev/run/7deb0902-eebb-47ce-ab19-b68844c9574b

The job also produced the shape reviewers most need to see: a step that did not complete. The wrap-up call was refused at the day's free limit, and the refusal filed its own public receipt, https://zambo.dev/run/7a64ca4a-036b-4152-86cf-cb956e1087db, instead of leaving a silence the summary could smooth over. Attached to a pull request, this is what proof of work means in practice: the claim, the chain under it, and the gaps visible as gaps.

When the trail is complete, it wraps into a handover: one link carrying the summary, the goal, the named recipient, and the full chain. A four-agent job wrapped this way sits at https://zambo.dev/handover/a154789b-0588-43c7-a31c-d108eb59406b. The reviewer Accepts or Flags; the merge conversation starts from evidence instead of from a description of evidence.

What proof of work does not prove

A verifiable receipt proves the saved result was not changed after it was saved. It does not prove the change is correct, the tests were meaningful, or the code should merge. A pull request can carry a perfect trail and still be the wrong change. What the trail removes is the unverifiable middle: the steps nobody can check, the outputs nobody can recompute, the "tests pass" nobody can audit. Review judgment stays human. The record stops being a matter of trust.

The scale of the record

Read live on November 16, 2026: 141,621 public receipts, 851 minted that day, 121,437 tool calls recorded, 430 workflow seals. Every receipt is checkable free at zambo.dev/verify, no account needed. Every tool is free once a day, plus 3 continue calls, with one free wrap-up handover per day and pickup always free. A Day Pass is $0.99 for 24 hours of lifted limits; the Zambo Pass is $29 for 30 days ($19 for $ZAMBO holders); the Lifetime Pass is $250, one payment.

A pull request from an agent should arrive the way work from a careful engineer arrives: with the evidence attached, ready to be checked.

Top comments (0)