Verify
Think of a signed Innsigle like a careful postage mark: it ties who sealed, what they declared about production, and which exact file they sealed. It is not a fact-checker and not an AI detector.
What VALID means
When innsigle verify prints VALID:
- The signature checks out for the issuer key
- The content SHA-256 matches the subject in the claim
- You can read the colophon (composition + ingredients) that was sealed
When the page is only marked and not signed, treat it as a declaration. still a valid use of the seal family, without cryptographic standing.
What it does not mean
- The prose is true or complete
- A platform or government certified the content
- Models were or were not used beyond what the colophon declares
Check it
curl -sL -o page.html https://documentdrivendx.github.io/innsigle/sample/
curl -sL -o att.json https://documentdrivendx.github.io/innsigle/sample/.well-known/innsigle/claims/index.attestation.json
curl -sL -o keys.json https://documentdrivendx.github.io/innsigle/sample/.well-known/innsigle/keys.json
npx innsigle verify --attestation att.json --content page.html --keys keys.json
Expect: VALID. Live: Sample.
Hierarchy on a verify view
- Primary: Signature valid or invalid; issuer when valid. Or “unsigned declaration.”
- Secondary: Composition and ingredient list (colophon).
- Tertiary: Content fingerprint, timestamps, raw claim download.
What the CLI checks
- Load attestation + keys
- Issuer public key present and not revoked
- SHA-256 of content matches subject digest
- Ed25519 over the canonical claim payload
| Layer | What it answers |
|---|---|
| Crypto valid | Did this key seal this colophon for these bytes? |
| Discovery | Absolute keys URL is inside the signed claim |
| Recognized | You pin that fingerprint, and/or follow key-endorsements (published statements naming another fingerprint). On this site the human key endorses the build key, so a generated-page seal can be recognized without pinning the CI key. |
| Derived page | The HTML colophon quotes the source attestation. VALID is for those markdown bytes, not the rendered HTML. |
issuer.id is a display slug and may collide. Prefer fingerprints.
Issuer documents can live on any durable HTTPS URL (gist, Pages, free host). A social bio issuer card is discovery only, not a signature. See Issuer.
Spec
Crypto: ADR-001. Issuer URL and web of trust: ADR-003. Human vs build keys, derived pages: ADR-004.
Innsigle seal: mixed by Innsigle (human key)
Signature covers the markdown source of this page, not these HTML bytes. This render quotes that seal.
- Composition
- mixed
- Issuer
- Innsigle
innsigle - Signing key
ed25519:15c6242b6ef825413847e221267959c9(human key)- Signed source
docs/website/content/curated/use/verify.md- Signed
- 2026-09-30T20:46:37Z
- Content digest
sha256:df5f762f…f7d1f0b4
Human-controlled key. Signature is not a detector and not a truth guarantee.
Raw attestation JSON
{
"payload": {
"innsigle": "1",
"type": "https://innsigle.dev/claim/colophon/v1",
"issued_at": "2026-09-30T20:46:37Z",
"issuer": {
"id": "innsigle",
"name": "Innsigle",
"key_id": "ed25519:15c6242b6ef825413847e221267959c9",
"key_url": "https://documentdrivendx.github.io/innsigle/.well-known/innsigle/keys.json"
},
"subjects": [
{
"uri": "https://documentdrivendx.github.io/innsigle/use/verify/",
"digest": {
"alg": "sha256",
"value": "df5f762f626be6dd7abd443a9e6f770f0bd79f9a660be75546cc7ef9f7d1f0b4"
}
}
],
"colophon": {
"schema_version": "1",
"composition": "mixed",
"ingredients": [
{
"kind": "human",
"name": "operator",
"role": "outline"
},
{
"kind": "model",
"name": "Claude",
"role": "expand"
},
{
"kind": "human",
"name": "operator",
"role": "final-edit"
}
],
"notes": null
}
},
"payload_encoding": "json",
"signatures": [
{
"key_id": "ed25519:15c6242b6ef825413847e221267959c9",
"alg": "ed25519",
"sig": "MD1uRin44bLFLJnsRpbmvD650ukCghqZHhqOjD7hsgeZcsGR5drJfIUEWf6LsNPKbsGXSKBCw-K_Alz8ALRHDg",
"signed_at": "2026-09-30T20:46:37Z"
}
]
}