The data viewer

One document from this site, rendered and raw.

The two views, and why they differ

Rendered is a reading of the parsed JSON: keys as labels, arrays as numbered cards, long strings and key material in their own blocks, and any key beginning _ shown as a note rather than payload — on this estate those carry the sentence disclaiming the file's own authority. Raw is the file's actual bytes, fetched as text and shown verbatim, not re-serialised: a raw view that pretty-printed a re-serialisation would be showing you something the file does not contain. The file is the source of truth; this page is presentation and holds no authority, exactly like the markdown reader it is modelled on.

What it will tell you

Where a document carries a sig and names its signer, the page verifies that signature in your browser — Web Crypto, ECDSA P-256/SHA-256, over the registry's canonical form, against the signing key published in the signer's own record. The check answers three ways and the third is not the second: verified, does-not-verify, and not-checked-here. An unavailable check is not a failed one, and this page will not render it as one. When a signature does verify, the page still says what that is worth: every root in this register is a fixture whose private half is published, so a verified signature carries integrity, not authority.

For agents

Fetch the .json directly. This page is for people; the documents are at their own stable URLs and always were. Every path under the registry's machine front door resolves without going through here.