Why Innsigle
You ship work in an AI-shaped world: models draft, platforms strip metadata, and readers still want a straight answer to how was this made? Badges that only celebrate “no AI” leave model-primary docs without a proud path. Industrial media pipelines do not center HTML docs or short posts.
Content provenance for the AI era is that problem: origin under your control, as a mark people can learn by sight.
The gap
| Approach | Example | Miss for makers |
|---|---|---|
| Human-only badges | Not By AI | No proud path for model-primary docs |
| Media credentials | C2PA | Social uploads strip metadata; not optimized for plain HTML docs or short social posts |
| Vendor watermark | SynthID | Not a maker-authored bill of production |
| Free-text footer | “Written with AI” | No shared mark or signature check |
You need one language for how work was made, usable for:
- Owned docs: a signed colophon that can name models without shame
- Human social posts: a mark that survives when file metadata dies
Innsigle is that language: the maker's seal under your control, across docs and social, with an optional signature over content bytes. C2PA and similar stay in their lane for industrial media, see Non-goals.
What you can check
We do not ask you to take the marketing on faith. The microsite ships a sealed sample you can re-verify with the CLI. That lets a reader check one binding: this issuer sealed this colophon for these bytes. It does not check whether the article is true.
Check it
What we claim: the published sample verifies under its live claim and keys.
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. Same recipe on CLI.
Next
- Install and seal
- Non-goals: category boundaries
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/why/index.md- Signed
- 2026-09-30T20:46:37Z
- Content digest
sha256:eaccd2b8…43c9905e
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/why/",
"digest": {
"alg": "sha256",
"value": "eaccd2b880327441f90be376cd2e0c460a152abb7dd18bc0607ed35043c9905e"
}
}
],
"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": "cwJVPd59DxDVJUb1zKB55_FQfTwE-TUfzC3mUCLdL9Zx9KDWsqViHa7tSCnpcuKrTZ5ddDaHGPyY7wV2NWrzDw",
"signed_at": "2026-09-30T20:46:37Z"
}
]
}