Generated from HELIX docs. Source:docs/helix/01-frame/features/FEAT-002-signed-docs-claims.md. Edit the source, not this file orsite/HTML.
Source frontmatter
ddx:
id: innsigle.feat.002
type: feature-specification
links:
- target: innsigle.prd
kind: informed_by
- target: innsigle.contract.001
kind: informed_by
- target: innsigle.adr.001
kind: informed_by
status: draft
activity: 01-frame
created: 2026-07-23
Feature Specification: FEAT-002 — Signed documentation claims
Feature ID: FEAT-002 Status: Specified Priority: P0 Owner: Operator Covered PRD Subsystem(s): UC-AI-docs; Sign and Verify; Tooling Distribution Covered PRD Requirements: FR-8–12, FR-18–19 Cross-Subsystem Rationale: Docs placement, claim binding, and CLI verify are one vertical for UC-AI-docs.
Overview
Operators publish static/HTML docs with an Innsigle, optional signed claim over file bytes, and offline verify (CONTRACT-001 / ADR-001).
Ideal Future State
Maker records colophon (named models/tools), places footer seal, signs with a local house key, publishes claim next to content. Third party verifies without an account. Tamper fails closed.
Problem Statement
- Current situation: CLI v0 + sample exist; need feature-level acceptance and walkthrough as product surface.
- Pain points: Docs lack portable signed BOM under maker control.
- Desired outcome: Documented happy path and automated tests for valid + mismatch.
Requirements
Functional
DOC-01. Maker publishes seal + bill on HTML/static page (inline or linked). DOC-02. Maker builds claim with content SHA-256 subject and colophon including named tools. DOC-03. Maker signs with local Ed25519 key; private key never published. DOC-04. Verify succeeds when sig valid, key active, content digest matches. DOC-05. Verify fails closed on content mutation (exit 3) and bad signature (exit 2). DOC-06. Verify output never includes detection scores.
Non-Functional
- Offline verify given claim + content + pubkey file.
- Golden vectors remain stable under ADR-001.
Acceptance sketches
| ID | Scenario | Expect |
|---|---|---|
| DOC-04 | Golden vectors CLI verify | exit 0, VALID |
| DOC-05 | Wrong content file | exit 3 |
| DOC-01 | Sample page footer | Links to attestation; model-primary bill visible |
Dependencies
- FEAT-001 composition language
- CONTRACT-001 CLI surface
Innsigle seal: model-primary by Innsigle (build key)
Signature covers the markdown source of this page, not these HTML bytes. This render quotes that seal.
- Composition
- model-primary
- Issuer
- Innsigle
innsigle - Signing key
ed25519:050bf4d0361a96aa3b6baa3fc2ffd0cb(build key)- Signed source
docs/website/content/generated/artifacts/features/feat-002-signed-docs-claims.md- Signed
- 2026-09-30T20:48:46Z
- Content digest
sha256:ca6b78d6…43bfc1ca
Endorsed by the human key for seal recognition (ADR-003).
Raw attestation JSON
{
"payload": {
"innsigle": "1",
"type": "https://innsigle.dev/claim/colophon/v1",
"issued_at": "2026-09-30T20:48:46Z",
"issuer": {
"id": "innsigle",
"name": "Innsigle",
"key_id": "ed25519:050bf4d0361a96aa3b6baa3fc2ffd0cb",
"key_url": "https://documentdrivendx.github.io/innsigle/.well-known/innsigle/keys.json"
},
"subjects": [
{
"uri": "https://documentdrivendx.github.io/innsigle/reference/artifacts/features/feat-002-signed-docs-claims/",
"digest": {
"alg": "sha256",
"value": "ca6b78d60393b882194fea11e2ef1cdb3309b4b1be49b916fa70874043bfc1ca"
}
}
],
"colophon": {
"schema_version": "1",
"composition": "model-primary",
"ingredients": [
{
"kind": "model",
"name": "Claude",
"role": "draft"
},
{
"kind": "tool",
"name": "sloptimizer",
"role": "rewrite"
},
{
"kind": "human",
"name": "operator",
"role": "structure-edit"
}
],
"notes": null
}
},
"payload_encoding": "json",
"signatures": [
{
"key_id": "ed25519:050bf4d0361a96aa3b6baa3fc2ffd0cb",
"alg": "ed25519",
"sig": "4BEFJpLVoRCIPZnmjwpXi9tG2gyoRKc2-1XPR4lZK8XPYp0Ttqf9SMzPKxYloficVKjRD7lkqq1yMrBVf51pCg",
"signed_at": "2026-09-30T20:48:46Z"
}
]
}