Innsigle Use Walkthrough: profile in your bio

Walkthrough: profile in your bio

You write in Google Docs, mail, and slides. You want people to see how a piece was made when they click the one link in your bio. You do not want to install Node or generate a key yet.

Goal

Publish a maker profile, put its URL in X / LinkedIn / Slack, and paste a footer line into a living document.

Steps

1. Build the page

Open Maker profile and fill Name and Profile id. Add one work: title, the Doc or deck URL, composition (mixed is the usual work default), optional model name. Download index.html.

Or from a clone:

innsigle profile init --id you --name "Your Name" --out-dir ./innsigle-profile
innsigle profile add --profile ./innsigle-profile/profile.json \
  --title "Q3 strategy memo" \
  --url https://example.com/memo \
  --kind mixed --model Claude

2. Host it

Drop the file (or the innsigle-profile/ folder) on GitHub Pages, Codeberg Pages, Netlify Drop, or any static HTTPS host. You need a durable URL. You do not need to run a server.

If the CLI wrote a marks/ folder, publish it next to index.html.

3. Put the URL in bios

Copy the bio card from the builder (or innsigle profile bio):

Innsigle · Your Name
https://you.github.io/innsigle/
SurfaceField
XWebsite / link field; optional "Innsigle" in the bio text
LinkedInContact / website
SlackProfile website (or a custom status that points at the same URL)

One URL everywhere. Do not paste raw keys.json into the bio.

4. Stamp the work

Paste the footer line at the end of the Google Doc, the last slide notes, or the email:

Innsigle · mixed · you.github.io/innsigle#q3-strategy-memo

That line is the plain seal. The profile row is the colophon.

5. What not to do

  • Do not hash the live Google Doc. It will drift. Stamp the living file; seal a PDF later if you need a signature.
  • Do not mark the work human-authored because a model draft was edited. That stays mixed or model-primary.
  • Do not tell readers the profile is VALID. VALID is only for signed bytes.

Check it

What we claim: you can produce a profile without keys, and verify still fails closed on that file.

innsigle profile validate --profile ./innsigle-profile/profile.json
innsigle verify --attestation ./innsigle-profile/profile.json \
  --content ./innsigle-profile/index.html \
  --keys ./innsigle-profile/profile.json

Expect: validate prints OK; verify exits 5.

Live example: sample maker profile.

Spec

Plain seals and maker profile

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-profile.md
Signed
2026-09-30T20:46:37Z
Content digest
sha256:1c4e9073…a66b44c9

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-profile/",
        "digest": {
          "alg": "sha256",
          "value": "1c4e9073380b7c74b3b9ae01d17c1cfd97824a71ffa641183e626ba9a66b44c9"
        }
      }
    ],
    "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": "RPrclKTXb-lbwNLWjc-DLdebNzfNdt75xwbfCQu-OIJLZrMu_h_jpu5C2Z5CV6RtSloPjAHJD7eTeb43QMJWAw",
      "signed_at": "2026-09-30T20:46:37Z"
    }
  ]
}