Typed Standards record: Example analysis

Type	`content/analysis/v1`
Role	analysis (asserted by the signer in extensions["role"]; not checked)
Status	`active`
Signer	`did:key:z6MkuSQz…AwYNzn` · Signed with a self-certifying key The signer's identifier is derived from the signing key, so it proves that the same key signed everything under this identifier, not who holds the key. No registry vouches for it, and the key cannot be rotated or revoked.
Name	calls itself “Example analyst” (the signer’s own description; not verified)
Binding tier	describes itself as `pseudonymous` (the signer’s own description; no check establishes it)
Envelope hash	`a171d1ab156d…`
Created	`2026-10-03T12:05:00.000Z` (the signer’s clock)
Source revision	`https://git.example.com/example/analysis`, commit `0123456789abcdef0123456789abcdef01234567`, path `notebooks/analysis.ipynb`, ref `refs/heads/main` (asserted; not fetched)
Summary	An example analysis notebook, executed end to end. (the signer’s)

verify: ok, no check contradicts the record

#1 Envelope integrity: verified
#2 Signature: valid
#3 Content canonicalization: ok, https://typedstandards.org/canonicalization/raw-bytes/v1
#4 Content hash: ok, sha256
#5 Key trust: Signed with a self-certifying key (self_certified; no registry vouches for it)
#6 Signing key id: ok
#7 Timestamp: no RFC 3161 token carried
#8 Transparency log: no log entry carried
#9 Referenced files: none
#10 Lifecycle: active (source: none)
#11 Capture method: script-run
#12 Type: ok, content/analysis/v1
#14 Signer identity: Signer identifier matches the signing key (key_derived_match)
#15 Capture method vocabulary: ok, scripted-recomputation
#16 Content profile: contentProfile_absent

This shows that the record is intact and which key signed it; it does not say the analysis is correct.