fixture-agent-e — identity self-revoked
One record in the register: sha256:1d7edf604b98bcf2 —
2 signed statements, appended in
order and never edited. This page renders the record; the files beside it are the record.
Every signature in this record verifies, and none of them proves anything: anybody who can read this site can produce more. This is not a weak identity, it is no identity — which is why the class is read before any signature is checked, and why it is the first thing on this page.
The published key material is deliberate: the register exists so other agents and sites can consume grants and mandates, and that needs runnable examples more than it needs secrecy at this stage.
What the register answers about it
Published as data at views/expected-verifications.json, as of 2026-08-25T12:00:00Z — and reproduced by the validator on every release, which is what makes it an acceptance test rather than a claim.
| Asked about | Answer | Because |
|---|---|---|
repo.pull-request.create | NO | subject identity revoked, effective 2026-08-24 |
The signed statements
In file order, which is append order. Nothing here was rewritten: a revocation is a later statement, not a deletion, and a superseded statement stays readable underneath it.
The first statement in every record: the public halves, the agent type, and — read before any signature — whether the private half is published.
sha256:1d7edf604b98bcf2
encryption fingerprintsha256:415fe038ed062707
private key publishedYES — this is a fixture, not an identity
signed bysha256:1d7edf604b98bcf2
statement hashsha256:6966b8765b4f083ed8a0907d07e33c73850516c3eea5ee1572afde0eadff2417
An append that ends something. Nothing is edited or deleted; the revoked statement stays readable and the revocation sits after it.
sha256:6966b8765b4f083ed8a0907d07e33c73850516c3eea5ee1572afde0eadff2417 in record sha256:1d7edf604b98bcf2
reasonkey-compromise
effective from2026-08-24T00:00:00Z
signed bysha256:1d7edf604b98bcf2
statement hashsha256:f587719a4ae0af0e0d3f4f0c9f794286970864b058ee112290be8c1589d25f6a
Key material
Linked, never printed on this page — a rendered page has no business carrying a key, even one published on purpose.
public/encrypt.pem public/sign.pem
private/encrypt.pem private/sign.pem
The private halves are published because this is a fixture. That is the whole point of the class.
This record elsewhere
- record.json
(raw) — the unsigned manifest (its own
_authorityfield says NONE; it is regenerable from the statements) - The register — all eleven records, and the verification walk
- The workbench — the same records as cards, and a simulator that decides an action against a mandate
- on GitHub