Innsigle Use CLI

CLI

Get a small tool that can declare how a file was made, optionally sign that declaration to the file bytes, and verify someone else’s seal. Node 20+.

Install

Not on the public npm registry yet. Install from GitHub or a clone.

From GitHub

npm install github:DocumentDrivenDX/innsigle
npx innsigle
# or: ./node_modules/.bin/innsigle

Global (optional):

npm install -g github:DocumentDrivenDX/innsigle
innsigle

From a clone

git clone https://github.com/DocumentDrivenDX/innsigle.git
cd innsigle
npm install -g . # or: npm link
innsigle

Without installing the bin, from the repo root:

node src/cli.mjs

Running with no arguments prints the command list (exit code 1).

Init a repo (1Password house key)

One-time setup. Needs op signed in. Writes only under .innsigle/ — no framework-specific publish tree.

innsigle init --onepassword --site-url https://example.com
# optional: --issuer-id my-house --vault Private
PathContents
.innsigle/config.jsonCommit-safe: key_id, key_url, 1Password op://… ref
.innsigle/public/keys.jsonPublic issuer document (staging)
.innsigle/AGENTS.mdHow agents copy staging into a site build
1Password Secure NotePrivate key only (not in git)

Publish contract (your build or an agent): copy .innsigle/public/ → site /.well-known/innsigle/ so keys are at https://…/.well-known/innsigle/keys.json.

After init, everyday commands stay short — repo config + 1Password supply the rest.

For a HELIX-style docs site, add --content-root so slugs match the content tree, then split keys (ADR-004):

innsigle init --onepassword --site-url https://example.com/ \
  --content-root docs/website/content
# then add keys.build + INNSIGLE_BUILD_KEY (CI); human key stays in 1Password
innsigle endorse --subject-key-id ed25519:… --purpose build-signing
innsigle seal --all --role human    # mixed / human-authored, locally
innsigle seal --all --role build    # generated, in CI
innsigle publish site
innsigle verify --all

Hugo mounts and the colophon partial: integrations/hugo.

Seal a page

# After init (preferred):
innsigle seal ./page.html
innsigle verify ./page.html

# Optional colophon control:
#   --kind model-primary|human-authored|mixed
#   or commit .innsigle/colo.json
#   or --colo path.json

# Manual keygen still available (no 1Password):
innsigle keygen --out-dir ./keys
innsigle keys template \
 --issuer-id my-house --issuer-name "My House" \
 --public-key "$(cat keys/ed25519.pub.raw.b64url)" \
 --key-id "$(cat keys/key-id.txt)" \
 --out keys.json
innsigle claim build --content ./page.html --colo colo.json \
 --issuer-id my-house --issuer-name "My House" \
 --key-id "$(cat keys/key-id.txt)" \
 --key-url https://example.com/.well-known/innsigle/keys.json \
 --out claim.json
innsigle sign --claim claim.json --key keys/ed25519.priv.pem --out att.json
innsigle verify --attestation att.json --content ./page.html --keys keys.json

Keep the private key offline (1Password via init, or local PEM). key_url must be an absolute URL; relative paths are rejected.

Config layers

LayerPathRole
Repo.innsigle/config.jsonIssuer, key_url, op:// private key ref
User (optional)~/.config/innsigle/config.jsone.g. default_composition
1Passwordvia op readPrivate key only

Check it (live sample)

What we claim: the microsite sample still verifies after install.

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.

Other commands

CommandRole
innsigle colo example --kind …Print example colophon JSON
innsigle seal --all / publishHelix microsite: seal every content_globs file; copy well-known
innsigle profile init / add / renderMaker page and plain (unsigned) seals; no keys
innsigle provenance build …Journal → detailed session provenance
innsigle provenance propose-colo …Session record → draft colophon

Next

Spec detail (flags, exit codes): claim and CLI contract.

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/cli.md
Signed
2026-09-30T20:46:37Z
Content digest
sha256:579f78ae…25951b40

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/cli/",
        "digest": {
          "alg": "sha256",
          "value": "579f78aef721e29a827ffd8898e8809b345169955447feb26666573f25951b40"
        }
      }
    ],
    "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": "LxPfC6TIjeWsxD_JmLsMVg5s5XXGg1BddGACaVWfdLinVII7BaYy-ZH1MwKz0Mz_JbQm3mPPeW3PDrfN7TAQAQ",
      "signed_at": "2026-09-30T20:46:37Z"
    }
  ]
}