site-session-2026-08-25 (authoring session of this registry)
One record in the register: sha256:f9facb4c94da6c19 —
1 signed statement, appended in
order and never edited. This page renders the record; the files beside it are the record.
The only record here whose signatures could mean something: private_key_published is
false, so the register can be asked about it and the answer is not circular. It is still signed by a
fixture root, so what it has is integrity, not authority — the two are independent, and the second
waits on a real enrolment.
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:f9facb4c94da6c19
encryption fingerprintsha256:cac36b2a1eefa53c
private key publishedno
signed bysha256:f9facb4c94da6c19
statement hashsha256:d7928e3c2d5874dd3600d6c16ffc359731d96a766608f650db5eb50b54cf6762
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
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