AISOURCEOFTRUTH.COM
RECORD · /r/862ccdff7b6bd479…

862ccdff7b6bd479f56e0d29e28f69cb5cf3ae63cc3d0c478de16700a3ed0826

ATTESTED record for asset /a/cb8fa771b809… · the asset's canonical page holds all versions, lineage, and corrections

WHAT THIS RECORD MEANS

promptreports-ai signed a record about one file, "Hire an agent: its own identity, a narrow scope, and an offboarding that reaches every product", and the registry logged it at 2026-11-12T16:23:11Z. The publisher says claude-opus-5-5 helped make it.

WHAT IT SHOWS

  • The file with this fingerprint is the one that was signed. One changed character breaks the match.
  • The holder of key promptreports-ai#1 signed it.
  • It was in the log by its appended time. Nobody can remove it or slip in an earlier one.

WHAT IT DOES NOT SHOW

  • That the content is true.
  • That the model named made it. That is the publisher's own statement.
  • Proof from an outside party. This publisher and the registry have the same operator.

The verdict below says whether to rely on it now. Who reads records like this · use cases

SIGNATURE VALID · Ed25519 APPENDED 2026-11-12T16:23:11Z PROOF READY IN 3 S COSIGNED 0 OF 2 · QUORUM NOT MET
VERDICT · AS OF CHECKPOINT 44

RELY

Rely on this record as of checkpoint 44: signed by an active key, no errata, no seal.

RULES CHECKED

Current through checkpoint 44, signed 2026-11-12T23:28:29Z; 0 of 2 required independent witness cosignatures (quorum not met). Checkpoint 44.

WHAT WOULD CHANGE THIS

  • If key promptreports-ai#1 is revoked from before 2026-11-12T16:23:11Z, when this record was signed, the verdict becomes do not rely; a revocation dated later makes it check. impact
  • An erratum or a seal on upstream record 3c533deac36ade2d… would make the verdict check. page
  • An erratum or a seal on upstream record 7a823218f79a76a2… would make the verdict check. page

as_of=44@2026-11-12T23:28:29Z · assess receipt · sha256 58ea48b508bffed7…

FAMILY · AS OF CHECKPOINT 44
2 upstreamderived-from 2amends 00 with errata0 sealed
0 downstreamderived-from 0amends 00 with errata0 sealed

Each count is a link that narrows the graph and the list below. A record counts under the link that reached it.

$ curl -H 'Accept: application/vnd.aisot.record+json' https://aisourceoftruth.com/r/862ccdff7b6bd479f56e0d29e28f69cb5cf3ae63cc3d0c478de16700a3ed0826 # this page is a rendering of the API. Reproduce it as data.
AS OF A SIGNED CHECKPOINT
LATEST4443

Pick a checkpoint to see the state the world model gives for it. A tree size shows its newest time: event rows filed after its checkpoint count once an anchor (within about 65 seconds) or the next checkpoint covers them.

PROVENANCE
publisherpromptreports-ai SAME OPERATOR · ATTESTED
artifacttext/markdown · "Hire an agent: its own identity, a narrow scope, and an offboarding that reaches every product" · cb8fa771b8095c79…
created bypromptreports-ai
modelclaude-opus-5-5
signing keypromptreports-ai#1 · Ed25519 · key directory
log index#42
PROOF AND WITNESSES

Proof in seconds, checked by outside witnesses

inclusion proofleaf 42 of 44 · first covered by a signed checkpoint 3 s after append · RFC 6962 audit path
checkpointsize 44 · root b2dea02300e4d175… · signed 2026-11-12T23:28:29Z · signed note
witness policy0 of 2 independent cosignatures on this checkpoint · tlog-policy NOT MET

A cosignature means a witness saw no fork or rollback of the log up to this checkpoint. It does not vouch for this record. Outside witnesses sign at their own interval, so cosignatures can lag the proof.

TIME

When it existed, from clocks we do not run

daily rootPENDING the next 06:00 UTC daily root covers it; its timestamps and Bitcoin anchor follow

Timestamps and the OpenTimestamps anchor are made over the daily root, the first one after the record was appended. Each checks without us: the token against the authority's root, the anchor against a Bitcoin block header.

DOWNLOAD RECEIPTS

Proof in the formats verifiers already read

FORMATFORGET IT
Sigstore bundle v0.3sigstore clients, with the registry's trusted rootGET /r/862ccdff7b6b…/sigstore-bundle
Export bundleverify.mjs, fully offlinePOST /v1/export
Signed recordthe exact signed bytes?format=record
Certificatepeople and auditors: every layer in one page/r/862ccdff7b6b…/certificate
$ curl -s -X POST https://aisourceoftruth.com/v1/export -H 'content-type: application/json' -d '{"digests":["862ccdff7b6bd479f56e0d29e28f69cb5cf3ae63cc3d0c478de16700a3ed0826"]}' -o bundle.json && curl -s https://aisourceoftruth.com/v1/export/verify.mjs -o verify.mjs && node verify.mjs bundle.json # check it offline
EMBED

Paste this next to the content the record describes. It links readers to this page and points crawlers and agents at the signed record.

badge preview

<a href="https://aisourceoftruth.com/r/862ccdff7b6bd479f56e0d29e28f69cb5cf3ae63cc3d0c478de16700a3ed0826" rel="noopener" title="Signed record on AI Source of Truth"><img src="https://aisourceoftruth.com/r/862ccdff7b6bd479f56e0d29e28f69cb5cf3ae63cc3d0c478de16700a3ed0826/badge.svg" alt="AI Source of Truth record 862ccdff7b6b" height="20"></a>
<link rel="alternate" type="application/vnd.aisot.record+json" href="https://aisourceoftruth.com/r/862ccdff7b6bd479f56e0d29e28f69cb5cf3ae63cc3d0c478de16700a3ed0826">
VERDICT BADGE

The verdict badge shows whether to rely on this record (rely, check or do not rely) and the signed checkpoint the verdict is pinned to. It shows a verdict, never a score, and links readers here.

verdict badge preview

HTML

<a href="https://aisourceoftruth.com/r/862ccdff7b6bd479f56e0d29e28f69cb5cf3ae63cc3d0c478de16700a3ed0826" rel="noopener" title="Verdict on AI Source of Truth"><img src="https://aisourceoftruth.com/badge/862ccdff7b6bd479f56e0d29e28f69cb5cf3ae63cc3d0c478de16700a3ed0826.svg" alt="AI Source of Truth verdict for record 862ccdff7b6b" height="20"></a>

Markdown

[![AI Source of Truth verdict for record 862ccdff7b6b](https://aisourceoftruth.com/badge/862ccdff7b6bd479f56e0d29e28f69cb5cf3ae63cc3d0c478de16700a3ed0826.svg)](https://aisourceoftruth.com/r/862ccdff7b6bd479f56e0d29e28f69cb5cf3ae63cc3d0c478de16700a3ed0826)

Script: checks the proof in the reader's browser

<script src="https://aisourceoftruth.com/badge/check.js?v=b305a52807c1" data-digest="862ccdff7b6bd479f56e0d29e28f69cb5cf3ae63cc3d0c478de16700a3ed0826" async></script><noscript><a href="https://aisourceoftruth.com/r/862ccdff7b6bd479f56e0d29e28f69cb5cf3ae63cc3d0c478de16700a3ed0826" rel="noopener" title="Verdict on AI Source of Truth"><img src="https://aisourceoftruth.com/badge/862ccdff7b6bd479f56e0d29e28f69cb5cf3ae63cc3d0c478de16700a3ed0826.svg" alt="AI Source of Truth verdict for record 862ccdff7b6b" height="20"></a></noscript>

The script form fetches this record's inclusion proof, the signed checkpoint and the log policy, and checks the log signature, the proof and the witness quorum with the browser's own WebCrypto before it draws "proof checked". Any failed check draws "proof failed" and names it. Where scripts are off, the image form shows instead.

RAW JSONDOWNLOAD SIGNED RECORDSIGSTORE BUNDLECERTIFICATELINEAGE →