Skip to main content

Agent-era builds · Stamp program

The stamp-ready badge

A buyer asks a vendor: can your agent emit a proper stamp? The badge answers that one question. It says the vendor's agent can emit thev0.1 stamp schema, seven blocks in order, digests computed the way the spec says. It says nothing else.

Spec v0.1.0 · Published 2026-11-04 · Status: current. Badge reviews are handled by hand while vendor demand is unproven.

What the badge means

Schema emission, and nothing more

A vendor's agent can emit the v0.1 stamp schema. That is all it means.

It is not a compliance certification. It is not legal advice. It is not an endorsement of the vendor's security, the agent's judgment, or the outcomes the agent produces. It does not say the agent is safe, careful, or honest. The honesty caveat from the spec applies here in full: a stamp is only as honest as the code that computes it, and a badge says nothing about that code.

To say the part plainly, because vendors will be tempted to say the opposite: there is no such thing as a Movahedi-certified agent. That phrase will never describe a badge holder, on this site or on theirs. Any vendor caught describing the badge that way loses it.

This stamp is an open evidence format for recording human approvals of agent actions. It is not legal advice, and it is not a movahedi.ca compliance certification.

That is the spec's non-certification disclaimer, repeated here word for word. Nothing may be added to it, nothing removed.

The review process

How a badge gets earned

The review works the way the crawler registry reviews a user-agent: a vendor submits evidence of emission, and movahedi.ca checks the evidence against the spec. The process is small on purpose, because the claim is small.

1. The vendor submits

Send three things through the contact form, with the subject line "Stamp-ready review": two stamps the agent emitted against a real draft, in the real v0.1 schema; a note saying which component of the vendor's system computes the digests and where it runs (the spec's honesty caveat sets the bar: digests should be computed where the approver controls them, and if they are not, say so); and the exact non-certification text the vendor's stamps carry.

2. The machine check

Both samples are parsed. The seven blocks must be present and in order. The digests are recomputed from the sample inputs and compared against the claimed values. The disclaimer must be byte-identical to the spec literal. Any mismatch, any missing block: the submission fails, and the reason is returned.

3. A person reads it

Machines check digests; only a person reads the attestation and the least-privilege scope and decides the submission is real work rather than a demo rigged for the test. This is the step that keeps the badge honest, and it is deliberately not automated.

What the review is not

It is not a code audit. It is not a penetration test. It is not an assessment of the vendor's security posture, development practices, or business legitimacy. A badge records that an agent emitted the right shape, on the samples it submitted, for spec v0.1. It says nothing about v0.2, and nothing about the vendor's next release.

The badge asset

Display it, linked back here

Stamp-ready badge

Download the SVG

Embed it like this:

<a href="https://movahedi.ca/agents/stamp-ready/"><img src="https://movahedi.ca/agents/stamp-ready/badge.svg" alt="Stamp-ready badge" width="220" height="72"></a>

Usage rules

  1. The badge must always link back to this page. A badge without the link is a violation, not a badge.
  2. Do not alter the mark. Resize is fine; redraw, recolor, or rewording is not.
  3. Do not place it beside claims it does not make: no "certified", no "compliant", no "approved". The disclaimer text on this page applies to every display of the badge.
  4. Never describe the badge as "Movahedi-certified" or your agent as a "Movahedi-certified agent". Both phrases are disavowed here and will be treated as misrepresentation.
  5. Misrepresenting the badge as a certification, a compliance mark, or legal approval revokes it. The listing comes down and the vendor is named in the revocation note.

Future work

A validator endpoint is parked, on purpose

A machine validator, an endpoint that takes a stamp and returns a verdict, is the obvious next build. It is parked. Hand review costs little while submissions are rare, and a validator that nobody uses is a promise to maintain. When vendor demand is real, the endpoint gets built and announced here. Until then, a person reads every submission.

The badge says the shape is right. The stamp says the approval is checkable. Whether to trust the agent is still your call.