Generated from HELIX docs. Source:docs/helix/01-frame/features/FEAT-005-plain-seals-and-maker-profile.md. Edit the source, not this file orsite/HTML.
Source frontmatter
ddx:
id: innsigle.feat.005
type: feature-specification
links:
- target: innsigle.prd
kind: informed_by
- target: innsigle.feat.001
kind: informed_by
- target: innsigle.feat.003
kind: informed_by
- target: innsigle.adr.003
kind: informed_by
- target: innsigle.contract.001
kind: informs
status: draft
activity: 01-frame
created: 2026-09-15
Feature Specification: FEAT-005 — Plain seals and maker profile
Feature ID: FEAT-005 Status: Specified (implemented: profile schema, CLI, site builder, sample page, tests) Priority: P1 Owner: Operator Covered PRD Subsystem(s): UC-human-social (generalized to email / Docs / slides); Visual Seal System; Tooling Covered PRD Requirements: FR-1–7, FR-13–16, FR-18; principle 5 (signet optional) Cross-Subsystem Rationale: Daily surfaces have no stable bytes. Plain seals reuse the colophon vocabulary without CONTRACT-001 digest/sign. The maker profile is the one bio URL.
Overview
Makers need to declare how a Google Doc, slide deck, or email was made without running keygen or hashing a file that will mutate. They also need one URL for X, LinkedIn, and Slack bios.
Ideal Future State
A maker opens the profile builder (or innsigle profile), names themselves, adds a work (title, URL, H/M/A), copies a footer line into the Doc, and publishes a static page. Bios point at that page. Keys and innsigle seal remain a later ladder, not a prerequisite. Verify never prints VALID for a plain seal.
Problem Statement
- Current situation: CLI and issuer card assume keys, a gist of
keys.json, and byte-stable subjects. - Pain points: Office/email/Docs users cannot start; bios have room for one link; signed claims do not fit living documents.
- Desired outcome: Unsigned plain seals + a Linktree-style profile page + builder, with tests and CI so the path stays honest (unsigned ≠ VALID, no authorship laundering).
Requirements
Functional
PLAIN-01. A plain seal carries composition + ingredients + subject title/URI. It MUST NOT require a content digest or issuer key. PLAIN-02. Type URI https://innsigle.dev/claim/plain-colophon/v1. Distinct from CONTRACT-001 colophon claims. PLAIN-03. innsigle verify MUST refuse plain seals and maker profiles (exit 5). It MUST NOT print VALID for them. PLAIN-04. human-authored MUST NOT list a kind: model ingredient (FR-4a). PLAIN-05. Product copy on the profile MUST label rows Unsigned declaration, never VALID / verified authentic.
PROF-01. A maker profile (innsigle_profile: "1") lists identity, optional social links, optional issuer discovery, and works[] of plain seals. PROF-02. CLI: profile init|add|render|footer|bio|validate. No 1Password. No .innsigle/ required. PROF-03. Site builder on /use/profile/ produces profile.json and standalone index.html in the browser (same renderer as CLI). PROF-04. Sample profile ships at /examples/profile/ and is regenerated at site build from fixture JSON. PROF-05. Bio card is name + profile URL. Issuer fingerprint is optional discovery on the same page, not a substitute for verify. PROF-06. Footer line for a work: Innsigle · {composition} · {host}#{slug}.
Non-Functional
- Profile HTML is self-contained (inline CSS; marks via href or inline SVG).
src/profile.mjshas nonode:imports so the browser builder can load it.- Unsigned path completes without Node when using the site builder.
Acceptance sketches
| ID | Scenario | Expect |
|---|---|---|
| PLAIN-03 | innsigle verify --attestation plain.json ... | exit 5; no VALID |
| PLAIN-04 | add work human-authored + model ingredient | refused |
| PROF-02 | profile init then add then render | index.html contains Unsigned declaration and the work title |
| PROF-03 | Playwright fills the builder | preview shows name + unsigned; download JSON validates |
| PROF-04 | site build | /examples/profile/ exists; no \bVALID\b |
Dependencies
- FEAT-001 composition language and mark pack
- FEAT-003 social discovery (profile URL replaces raw keys.json in bios)
- ADR-003 D7 (profile is discovery; crypto still lives in signed claims)
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-005-plain-seals-and-maker-profile.md- Signed
- 2026-09-30T20:48:46Z
- Content digest
sha256:ce6e2aa8…ddb5b655
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-005-plain-seals-and-maker-profile/",
"digest": {
"alg": "sha256",
"value": "ce6e2aa876db59c21fa6449928ea599acbc4feed61e6f6d51b66c080ddb5b655"
}
}
],
"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": "Ktw1wa2lewom5vkXcQwACDciR6-UlQ_D2Y0ODQn7is9MsErjQkrx3z7nfAPTCFd_qr9YK7fH7JthCuo7GdPMCw",
"signed_at": "2026-09-30T20:48:46Z"
}
]
}