The maker's seal for published work
Model-heavy docs and human posts share one problem: readers cannot see how the piece was made, and platforms strip the metadata that might have told them.
Innsigle (say INN-siggle, rhymes with single) is a craft seal for that gap: a visible mark, a short colophon of how the piece was made (human-authored, mixed, or model-primary), and an optional house or person signature over the content bytes.
Readers can learn the mark by sight: a sigil of care. The publisher put how the work was made on the record. Same seal family for model-heavy docs and human social posts.
Two jobs, one system
Docs (model-primary, proud)
Long-lived documentation often starts with models. Name the tools on the colophon (Claude, sloptimizer, …). Sign with a house key when you want readers to verify that your issuer sealed this colophon for these bytes.
Social (human-authored, clear)
Short posts strip file metadata. Use the same seal family with a human cue and a link out. Visibility first; per-post crypto optional.
What a seal actually guarantees
When a claim is signed, verification answers one question: did this issuer seal this colophon for these content bytes? It does not say whether the prose is true. An unsigned mark is still a valid Innsigle; the signature is optional depth, not a tax on using the mark.
Check it
What we claim: the published sample is sealed to its exact file bytes.
npm install github:DocumentDrivenDX/innsigle
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 page: Sample.
Start here
- Make a profile: unsigned seals for Docs, mail, and slides (no keys)
- See the sealed sample: model-primary page you can re-verify
- Install the CLI: keygen, claim, sign, verify
- Seal a docs page: full walkthrough
- Why Innsigle: gap vs badges, C2PA, watermarks
- Non-goals: not a detector, not a purity product
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/index.md- Signed
- 2026-09-30T20:46:37Z
- Content digest
sha256:0465d60a…53b4c0c1
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/",
"digest": {
"alg": "sha256",
"value": "0465d60a411756b722d7e101ff7e85cd7ce22ea5ddb7847d0f16a72153b4c0c1"
}
}
],
"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": "NHnLBFX0_uWM2ZRUMO2OSPqIXyKXWOA4JpeCWuihs0AKG7B0B2yGkl6SjKkPM55pf3X3cC5yXCxTTCsU6N2hBw",
"signed_at": "2026-09-30T20:46:37Z"
}
]
}