Walkthrough: human social mark
You wrote the post yourself. Many platforms strip or hide file metadata. You still want the same Innsigle seal family as your docs, with a clear human cue, and you do not want to run a webserver.
Goal
Mark a short post as human-authored so viewers can see composition without a purity lecture and without depending on C2PA surviving upload.
Steps
1. Confirm composition
Only use human-authored when humans produced the substantive words. Do not mark model-primary text as human because it was sloptimized.
2. Publish issuer metadata (no server)
If you sign anything (optional for social, required when you do sign):
keygen+keys template→issuer.json- Host the public file on a free HTTPS host (GitHub Gist raw, Codeberg, Pages, …)
- That absolute URL is your
key_url
See Issuer identity.
3. Point the bio at a maker profile (or an issuer card)
Preferred: publish a maker profile and put that URL in the website / link field. Keys are optional.
If you already publish keys, you MAY also embed an issuer card in bio / about:
Innsigle · Your Name
key ed25519:YOUR_FINGERPRINT_HERE
keys https://gist.githubusercontent.com/you/…/raw/issuer.json
Link field → the same keys URL. This is discovery, not a seal.
4. Export the mark
Use the H cue from the mark pack:
- Repo:
docs/sample/assets/marks/innsigle-human.svg - Site catalog: Marks
Render to PNG at 128×128 if the platform prefers raster attachments.
5. Place on the post
Pick one or both:
- Image: attach the mark still (or composite into a card).
- Link: short URL to how-to-read (e.g. site Use → Marks) and/or your keys URL.
Example caption skeleton:
Human-authored. Innsigle mark: H.
key ed25519:… · keys https://…
How to read: https://documentdrivendx.github.io/innsigle/use/marks/
6. What not to do
- Do not rely on C2PA in the image surviving upload.
- Do not use a different “purity” logo for human posts only.
- Do not claim the platform verified authenticity.
- Do not upload your private key anywhere.
Same family as docs
Model-primary docs use the A cue; human posts use H. Both are Innsigle. See the home dual-job story and Non-goals.
Spec
Feature note: human social mark
Captures
Add before/after post screenshots under docs/website/static/captures/ when available (e.g. walkthrough-social-x.png).
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/walkthrough-social.md- Signed
- 2026-09-30T20:46:37Z
- Content digest
sha256:491e6382…b335fb1e
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/walkthrough-social/",
"digest": {
"alg": "sha256",
"value": "491e63825f7accbcf67e6bca3005a9372f43818abf65bb012d028f94b335fb1e"
}
}
],
"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": "zGGoxU5WGf31-9e-laHBp4Q_-3YltjWw0mbVB3FMIKNckXdNwGlHUZUb-ibc-zBRBV6f_3-JXb2GFeNa-Ln5Cw",
"signed_at": "2026-09-30T20:46:37Z"
}
]
}