Generated from HELIX docs. Source:docs/helix/01-frame/prd.md. Edit the source, not this file orsite/HTML.
Source frontmatter
ddx:
id: innsigle.prd
type: prd
kind: product
links:
- target: innsigle.product-vision
kind: informed_by
- target: innsigle.competitive-analysis
kind: informed_by
- target: innsigle.research.prior-art
kind: informed_by
- target: innsigle.research.naming
kind: informed_by
- target: innsigle.principles
kind: informs
- target: innsigle.concerns
kind: informs
status: draft
product_name: Innsigle
activity: 01-frame
created: 2026-07-22
updated: 2026-07-25
Product Requirements Document
Summary
Innsigle is the maker's seal for published work—a content-origin seal for makers (publishers/operators) who publish in two channels. Category: content provenance for the AI era.
- UC-AI-docs: Owned documentation (e.g. HELIX microsite): model-primary
content with a signed colophon that can proudly name tools (e.g. Claude) and a house/person signer.
- UC-human-social: Short posts on X/Twitter and similar: a human-authored
mark that stays visible when platforms strip file metadata.
Same seal family; different colophons. Optional DKIM-style signing for durable content. Not an AI detector. Not a C2PA replacement (C2PA/SynthID serve media pipelines and vendor watermarks; social text and proud model BOM are the gap).
v1: Mark system + colophon model + docs sign/verify CLI + social placement pattern (image/link). Sample on operator docs and social first. Editorial tooling such as sloptimizer (easel-skills) is a complementary pipeline step: list it on the bill when used; it does not change composition to human-authored.
Name: Innsigle (INN-siggle, rhymes with single).
Problem and Goals
Problem
Two concrete failures for the same operator:
| Use case | Failure today | Why substitutes fail |
|---|---|---|
| Model-heavy docs site | No signed, portable BOM that credits models by name under a house seal | C2PA is media-file heavy; SynthID is vendor signal without maker bill; footers are unsigned and easy to ignore |
| Human posts on X/etc. | No maker-controlled human mark that survives the channel | Not By AI is human-only product culture, not dual system; C2PA metadata dies on upload; platform labels are not portable |
Competitive layer map (see competitive-analysis.md): badges, C2PA, watermarks, IPTC codes, platform labels, and detectors each cover a slice; none cover both UCs as one brand + claim system.
Goals
- UC-AI-docs: Operator can publish docs with an Innsigle whose colophon
names generative tools and is optionally signed so readers verify house/person sealed that bill for those content bytes.
- UC-human-social: Operator can mark a short social post as human-authored
with the same seal family, without depending on embedded file manifests.
- Product copy never markets detection or treats AI composition as a lesser
class of seal.
Success Metrics
| Metric | Target | Measurement Method |
|---|---|---|
| UC-AI-docs live sample | ≥1 real docs property (e.g. HELIX or Azgaard docs) shows Innsigle + colophon with named model; signed path works for at least one canonical page | Checklist + verify CLI against live URL or published artifact |
| UC-human-social live sample | ≥1 real X (or equivalent) post or profile asset uses human-authored Innsigle pattern | Screenshot + placement checklist |
| Docs sign/verify | 100% P0 fixtures verify; mutation and wrong key fail closed | Automated CLI/crypto tests |
| Unsigned social place | Human mark pack placeable in ≤15 minutes without account | Timed task n≥3 |
| Composition literacy | ≥50% surveyed readers describe mark as how-made / composition | Survey at launch; separate docs vs social samples if possible |
| Category integrity | Zero public detection-accuracy claims | Release checklist |
Non-Goals
- AI content detection or decoding SynthID/Video Seal (the FR-20 human-input
measure is a maker declaration derived from the maker's own session journal, not detection of unknown text).
- Replacing C2PA/CAI as the media industry standard or camera capture chain.
- Guaranteeing colophon factual truth (only declaration + optional signature).
- Multi-tenant accounts, marketplace, or social network in v1.
- Native X API integration or platform partnership as P0.
- EU AI Act certification product.
- Requiring signed claims on ephemeral social posts.
- Treating prose de-AI-ifying (e.g. sloptimizer rewrite) as proof of
human-authored composition or as an authorship detector.
- Absorbing sloptimizer into Innsigle; they remain separate tools that can run
in sequence.
Users and Scope
Primary Persona: Dual-channel operator (Erik / Azgaard)
Role: Builds methodology docs with models; posts human writing on social Goals: Proud model BOM on docs; clear human mark on social; one system Pain: Tools force either human-only badge culture or industrial media provenance
Secondary Persona: Docs reader
Role: Developer or practitioner reading sealed documentation Goals: See which models/tools produced the page; optional verify signer Pain: Unclear whether docs are human, model, or mixed; no trust anchor
Tertiary Persona: Social viewer
Role: Follower on X/similar Goals: Tell human-authored posts from unlabeled AI sludge at a glance Pain: Platform labels incomplete; metadata invisible
Requirements
Must Have (P0)
- Colophon model: at least human-authored, model-primary (AI-generated), and
mixed; tools/models nameable (e.g. Claude).
- Visual seal family usable for both composition poles (not separate good/bad logos).
- UC-AI-docs: Embed mark + colophon on a static/HTML docs page; optional
sign and verify for canonical content.
- UC-human-social: Placement pattern for human-authored posts when file
metadata cannot be trusted (mark image and/or short verify/profile link).
- Public "what this is not" (not detector; not C2PA replacement).
- Runnable sign/verify tooling for the docs path (CLI or equivalent).
Should Have (P1)
- Brand/docs site teaching both use cases in ≤5 minutes.
- House signer profile (Azgaard) as default sample issuer.
- Site-generator notes (e.g. Hugo/static footer partial).
- Social asset pack (avatar-adjacent mark, post image template, caption templates).
- Documented sample recipe: model draft → sloptimizer → Innsigle bill/sign for
methodology docs (links to easel-skills sloptimizer; no merge of codebases).
Nice to Have (P2)
- C2PA export/bridge for image assets.
- IPTC
digitalSourceTypemapping from colophon fields. - Hosted key directory.
- Native platform integrations.
- ~~Quantitative percentages in colophon.~~ Promoted to FR-20/FR-20a (declared human-input measure).
- Optional agent/skill hook that proposes a colophon after a sloptimizer pass
(still human-confirmed composition state).
Functional Requirements
Subsystem: Colophon Model
- FR-1 Colophon includes composition states at least:
human-authored,
model-primary (AI-generated), mixed.
- FR-2 Colophon can list named tools/models (e.g. Claude, other LLMs,
image models), editorial tools (e.g. sloptimizer), and human roles (edit, structure, review).
- FR-3 No required ranking of states as better/worse; AI-named bills are
valid first-class seals (model credit is an allowed primary use).
- FR-4 Product defaults and mark variants do not encode human = good /
AI = bad.
- FR-4a Composition state is independent of prose "AI-tell" cleanliness:
an editorial rewrite (including sloptimizer) must not, by itself, flip model-primary or mixed to human-authored. Guidelines state this boundary.
- FR-20 Colophon MAY carry a declared, evidence-derived human-input measure
(human_input): an integer percent computed from the maker's own session journal by a versioned method (hi1 weighs direction, contribution, and review), recorded with the raw counts and weights so any holder can recompute it.
- FR-20a The measure is a maker declaration, never a detection verdict:
omitted when journal evidence is absent (never invented), and product surfaces MUST NOT present it as an AI-detection score or purity ranking.
- FR-21–FR-25 Signed human review claims, derivation across a build, and
stable document keying (FEAT-006, ADR-005): a review binds a human-role key to a content digest without changing composition; verify --all --require-review is the publish gate; a derivation claim carries the review to built outputs.
Subsystem: Visual Seal System
- FR-5 Seal assets form one visual family across composition states; variants
may signal state without purity/shame coding.
- FR-6 Placement guidelines cover (a) docs site footer / about, (b) social
mark image or link pattern.
- FR-7 Guidelines forbid "verified real content" / oracle-truth motifs.
Subsystem: UC-AI-docs (documentation)
- FR-8 Maker can publish an Innsigle on an HTML/static docs page with colo
inline or one link away, including named models.
- FR-9 Maker can sign a claim over a defined canonical content unit (page or
artifact) binding: content fingerprint, colophon, issuer, time.
- FR-10 Third party verifies claim + content + issuer public key; fails
closed on mutation or key mismatch.
- FR-11 v1 signing uses maker-controlled local keys; no hosted account required.
- FR-12 Verify output reports validity and signer, not a detection verdict.
Subsystem: UC-human-social
- FR-13 Maker can mark a short social post as
human-authoredusing assets
or patterns that do not require surviving C2PA/EXIF on the platform.
- FR-14 Social pattern includes a path for viewers to learn mark meaning
(profile link, site, or short URL); unsigned is allowed.
- FR-15 Social human mark uses the same seal family as docs (not a separate
human-only brand product).
Subsystem: Brand Site and Education
- FR-16 Public explainer documents both UCs, colophon examples (Claude-named
docs, optionally with sloptimizer on the bill; human social), verify when signed, non-goals, and the sloptimizer complement (edit vs seal; no authorship laundering). Brand lines (byte-exact, straight '): home H1 and footer chrome use The maker's seal for published work; category line Content provenance for the AI era on Non-goals/meta—not as sole footer pitch. Seal/mark ≠ signet (unsigned seals valid). Maker = publisher/operator. Sigil at most once in home or Marks body plus glossary; no occult register.
- FR-17 Pronunciation documented once: INN-siggle (rhymes with single).
Subsystem: Tooling Distribution
- FR-18 Assert/sign/verify tooling ships documented and runnable for UC-AI-docs
P0 without a GUI.
- FR-19 Tooling accepts a colophon that includes named generative tools.
Acceptance Test Sketches
| Requirement | Scenario | Input | Expected Output |
|---|---|---|---|
| FR-1–4, FR-4a, FR-8, FR-19 | HELIX-like docs page, model-primary | Colophon: Claude draft, sloptimizer rewrite, human edit; footer seal | Reader sees named model and editorial tool; state remains model-primary |
| FR-9–12, FR-18 | Sign docs page | Canonical HTML or content bytes + house key | Verify succeeds; bit-flip fails; wrong key fails |
| FR-5–7, FR-13–15 | Human X post | Human-authored mark asset or link pattern | Viewer can see human composition without file metadata |
| FR-16–17 | New visitor | Brand site only | H1/footer B4; Non-goals/meta A1; both UCs; sloptimizer ≠ human authorship; detector only on Non-goals; INN-siggle once; no Colo· chrome |
Technical Context
Assumptions until ADRs:
| Area | Choice |
|---|---|
| Language/runtime | TypeScript + Bun for CLI |
| Crypto | Sign content hash + claim payload (algorithm in ADR) |
| Key discovery v1 | Public key URL / well-known path; no IdP |
| Docs channel | Static HTML sites (Hugo-class); footer + claim URL |
| Social channel | Visible mark image + optional URL; no dependency on platform preserving manifests |
| Out of v1 | Central claim DB, multi-tenant auth, X API bot |
Constraints, Assumptions, Dependencies
Constraints
| Kind | Constraint |
|---|---|
| Channel | Social platforms strip or ignore signed media metadata; design UC-human-social accordingly |
| Technical | Docs verify offline given claim + content + pubkey |
| Business | Operator live samples first (Azgaard / HELIX docs + social) |
| Brand | Visual seal primary |
| Competitive | Do not market as C2PA or SynthID replacement |
| Integrity | Editorial tools that reduce AI-tell patterns do not redefine composition state |
Assumptions
- Naming models (Claude, etc.) in a public bill is desirable for UC-AI-docs.
- Naming editorial tools (sloptimizer) on the bill is desirable when used.
- Human social often stays unsigned; in v1, visible mark placement matters more than per-post signatures.
- Local keys acceptable for house signing of docs.
- Sloptimizer remains in easel-skills; Innsigle does not reimplement Vale prose rules.
- Competitive analysis in
docs/helix/00-discover/competitive-analysis.mdremains the rivalry baseline until next research pass.
Dependencies
- Competitive analysis and vision (this pass)
- Seal mark design (open)
- Claim format ADR/contract (open)
- Domain for verify URLs (open)
- Optional: easel-skills sloptimizer available in operator agent environment for sample recipe
Risks
| Risk | Probability | Impact | Mitigation |
|---|---|---|---|
| Docs path collapses into "just use C2PA" | Med | High | Scope: maker BOM + house sign for HTML; C2PA bridge is P2 |
| Social mark ignored as random SVG | Med | High | Strong mark design; profile/about education; sample consistency |
| Proud AI bill read as greenwashing | Med | Med | Exact tool names + human roles in bill; no "authentic" oracle language |
| Human mark forks into Not By AI clone | Med | Med | Dual-UC brand rules; same family as model-primary seals |
| Scope creep to detectors or platform deals | Med | High | Non-goals; P0 = live-sample UCs only |
| "Sloptimized = human" laundering | Med | High | FR-4a; guidelines; brand explainer; non-goal |
Open Questions
Design drafts: docs/helix/02-design/ (DESIGN.md, claim-system.md, attestation-prior-art.md). Remaining freezes:
- [ ] Canonical content unit for multi-page docs (per-page vs release set)
- [ ] HTML canonicalization for hashing (Contract)
- [ ] Signature algorithm + envelope freeze (ADR; draft proposes Ed25519)
- [ ] Seal glyph geometry and state cues (DESIGN.md open list)
- [ ] Product domain vs
*.azgaard.netfor type URIs and key_url - [ ] Model version pins in colophon v1
- [ ] Claim URL shape for social (profile well-known vs per-post)
Success Criteria
- UC-AI-docs live on at least one operator docs property with named-model colophon;
signed verify path green on one canonical artifact.
- UC-human-social live as at least one real human-authored social placement.
- Automated sign/verify tests green; no detection claims in public materials.
- Competitive non-goals held: not C2PA replacement, not detector.
Review Checklist
- [x] Summary is a 1-pager including both UCs
- [x] Problem tied to competitive gaps
- [x] Goals map to UC-AI-docs and UC-human-social
- [x] Metrics cover live samples on both channels
- [x] FR-n cover colophon, docs sign, social pattern
- [x] Non-goals exclude C2PA war and detectors
- [x] Acceptance sketches cover both UCs
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/prd.md- Signed
- 2026-11-10T13:38:16Z
- Content digest
sha256:7e92d0a8…8dcae411
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-11-10T13:38:16Z",
"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/prd/",
"digest": {
"alg": "sha256",
"value": "7e92d0a82c6c8b29016b82a9d2869afe7620c952887fdee7c002bf138dcae411"
}
}
],
"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": "PYzF-8GcgMjlvTneFk0kMjv7sAYHXx5_fPS-tfMLS1Qhuis3zvEbS9pgJc1yCxymfecfrYVIrohbRtksAV1TDQ",
"signed_at": "2026-11-10T13:38:16Z"
}
]
}