Urgent.News

What's breaking now, across thousands of outlets.

Tech

AER-1: the open standard for agent execution receipts

A standard is not a document. A document plus a published test corpus, plus independent implementations written by people who owe you nothing, plus a production stream anyone can audit: that is a standard. AER-1 has all four, and the numbers are public. As of today, November 15, 2026, the origin product has minted 140,344 public AER-1 receipts , 2,234 of them today, across 120,557 recorded tool…

AER-1 is an open standard for agent execution receipts, defined in the IETF Internet-Draft draft-zambo-aer1-26. Brennan Zambo created this standard, and it is based on a document plus a published test corpus and independent implementations. As of November 15, 2026, there have been 140,344 public AER-1 receipts minted by the origin product, with 2,234 of them issued today across 120,557 recorded tool calls and 430 workflow seals.

The packages carrying the format have been downloaded 270,700 times. Each receipt records a single agent tool call, including the tool name and version, inputs, saved result, and execution time. A SHA-256 commitment is computed over the canonical bytes at execution time. AER-1 receipts are open and recomputable by anyone, without any account.

The format ensures that the saved result cannot be changed since it was saved, but it does not prove the answer's correctness. The conformance corpus, containing 143 vectors and 146 checks, is published on zambo.dev/aer1/corpus.json, ensuring that every runner tests the identical set. Independent implementations of AER-1 include ARION, ColonistOne, and MasterD, all built from the draft text alone.

The standard is not a finalized RFC but an independent submission, with its claim to being the standard resting on the published draft, digest-pinned corpus, independent implementations, and 140,344 production receipts that anyone can recompute.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

WordPress published a change nobody re-approved: the SHA-256 fix

WordPress published a change nobody re-approved: the SHA-256 fix A writer drafts. A reviewer signs it off. An hour before launch, somebody fixes "just a typo" — except the typo was the price in the…

  • WordPress published SHA-256 fix change without approval
  • Approval process flawed, doesn't guarantee content approval
  • Fix addresses text fields, not images or custom fields

GLIBCXX_3.4.29 not found - and why copying libstdc++ does not fix it

Short answer GLIBCXX_3.4.29 is a version tag in libstdc++ (the C++ standard library shipped with GCC), not in glibc. The binary was built with a newer GCC than the target host has, so the target's…

  • "GLIBCXX3.4.29 not found" error occurs due to version mismatch between binary and C library.
  • Copying libstdc++ file does not fix the issue, deeper glibc error persists.

More from Sunday 15 November →