Versions and changelog
Rendered from emailing/CHANGELOG.md in the Common Agent Standards repository, at commit 16beb9fa.
Versions#
The specification is published one version at a time. This site carries version 0.2.1, dated 2026-10-29, and the specification page names it at the top.
The source of every version is in the Common Agent Standards repository, where each version is tagged as emailing-v followed by the version. A tagged version is also kept at an address of its own: 0.2.0, 0.2.1. The main branch, which can be ahead of the published version, is rendered at agentemailing.ai/draft/.
| Version | Date | What it changed |
|---|---|---|
| 0.2.1 | 2026-10-29 | No change to the text of the specification |
| 0.2.0 | 2026-10-29 | The human part becomes required and is generated from the envelope (§3.3) |
| 0.1.0 | 2026-10-29 | The first version |
Changelog#
The changelog is part of the standard's source and is reproduced here in full, newest first.
0.2.1 (2026-10-29)
No change to the text of the specification. This version publishes agentemailing.ai with a Get started page (/getting-started.html) that runs the Agent Emailing Server (https://github.com/Agent-Emailing/agent-emailing-server) for one agent and says how to run the conformance cases against any implementation, and with an Implementations section on the Email providers page that names the reference implementation and says, for each provider adapter, whether it has carried real signed email or was tested against the provider's documentation only. The specification page notes, under Section 12, where the reference implementation and the cases are. A version of this specification is what publishes the site's root, so a page of the site is published with a patch version. No requirement, member, attribute or section number changes.
0.2.0 (2026-10-29)
The human part becomes required and is generated from the envelope (§3.3). It
states who sent the email and for whom, what was asked, what was handed over,
the outcome, the price and what happens next. The subject carries the offering
and the state, such as "Book a meeting — done". The envelope's
meta.agent_emailing signs the text's digest and the subject, and software
that shows the text to a person checks it and warns when it differs. A
carrier should leave the text part unchanged, and the carrier test checks the
text's digest. A mail program is a fifth conformance role. The fixtures follow
these rules: the example thread grows to four emails, case e18 covers a human
part that disagrees with its envelope, and case e19 a forgery that fails the
signature, the name card and the text checks.
0.1.0 (2026-10-29)
The first version. A signed Agent Messaging envelope travels as an attachment in an ordinary email, files travel beside it pinned by digests, and headers are hints only. It defines native and bridged modes, the verified email endpoint on a name card, the minimum sending setup, the receiver protections of Agent Messaging §22 with the mailbox window, delivery signals, sealing, task ordering, what an email provider must and should support, and conformance fixtures a provider can run.