Walkthrough: conversation → document → colophon
You prompt two agents. They each write a markdown page. You want more than a finished file. You want a journal, a session record, and a proposed colophon you can seal to the bytes.
This page is the story, not the raw JSON. Three human prompts go into agent sessions (Claude and Codex in the fixture). The Innsigle session skill builds session provenance and proposes a colophon.
Spec detail (optional): session provenance feature.
Human prompts → agent writes markdown → journal + L2 provenance → colo.json
↓
review · optional sign
Step 1: Human prompts
The operator types these (same sequence for each agent in the fixture):
Draft a short markdown page titled Sealed Notes explaining what an Innsigle colophon is in two paragraphs.
Add a bullet list of three non-goals: no AI detection, no purity score, no claim of content truth.
Tighten the opening sentence; keep model-primary honesty.
Full list: human-inputs.json.
Step 2: Agent writes the document
The model produces a markdown file (model-primary: the agent wrote the bytes).
Writes sealed-notes-claude.md: two paragraphs on the colophon, then the non-goals list.
The document (Claude session)
Sealed Notes
An Innsigle colophon declares how a piece of work was made, composition and ingredients, not whether the prose is true or pure.
It lists models, tools, and human roles so readers can see how the piece was produced.
Non-goals
- No AI detection
- No purity score
- No claim of content truth
Codex produces a parallel page: sealed-notes-codex.md. Claude artifact: sealed-notes-claude.md.
Step 3: Skill captures the session
The harness records a journal (JSONL): each human prompt, assistant turn, file write (by: model), tool/skill calls. That is not the colo yet; it is the raw machine log.
From the merged Claude + Codex journals the driver reports:
| Metric | Value |
|---|---|
| User prompts | 6 (3 per agent) |
| Assistant turns | 5 |
| Models | Claude, Codex |
| Composition suggestion | model-primary |
Rewrite tools (e.g. sloptimizer) appear as ingredients. They do not turn the work into human-authored.
Step 4: Proposed colophon
This is what a reader (or claim) should show next to the document:
Colophon · model-primary
| Kind | Name | Role |
|---|---|---|
| model | Claude | primary |
| model | Codex | primary |
| tool | innsigle-session | provenance-capture |
| tool | sloptimizer | rewrite |
| human | operator | prompter |
session metrics: user_prompts=6; assistant_turns=5
Linked provenance: session-provenance.json
Machine form: colo.json.
Step 5: How it looks on a sealed page
Footer pattern (same idea as the Sample signed page):
When you sign, the claim binds content SHA-256 + this colo + absolute issuer key_url. Verification checks the seal, not whether the prose is true.
Reproduce
npm run test:provenance-driver
Check it
Expect the driver to propose model-primary with models + tools (including rewrite tools) listed as ingredients, not a flip to human-authored. Details: Session provenance.
Issuer without a server: Issuer identity.
Machine pack
| File | Role |
|---|---|
| human-inputs.json | Prompts |
| session-claude.jsonl | Claude journal |
| session-codex.jsonl | Codex journal |
| session-provenance.json | Session record |
| colo.json | Proposed colo |
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-provenance.md- Signed
- 2026-09-30T20:46:37Z
- Content digest
sha256:37f5b183…faf49d73
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-provenance/",
"digest": {
"alg": "sha256",
"value": "37f5b1834cb83fac8023f1f7c3de458187f8e3d30f916efe5e145f1bfaf49d73"
}
}
],
"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": "dWTK3Jc1g_RscVzD41ynyD3iWcYLwyuXMFi03VixbWqOloneHYsB-GFdcYWXiYml03FMysEjzyEnPZ8BESuLBA",
"signed_at": "2026-09-30T20:46:37Z"
}
]
}