Feature Specification: FEAT-003 — Human social mark pattern: Innsigle

Generated reference: edit sources under docs/helix/, then npm run site:build.

Generated from HELIX docs. Source: docs/helix/01-frame/features/FEAT-003-human-social-mark.md. Edit the source, not this file or site/ HTML.

Source frontmatter

ddx:
  id: aibadge.feat.003
  type: feature-specification
  links:
    - target: aibadge.prd
      kind: informed_by
    - target: aibadge.feat.001
      kind: informed_by
status: draft
activity: 01-frame
created: 2026-07-23

Feature ID: FEAT-003 Status: Specified Priority: P0 Owner: Operator Covered PRD Subsystem(s): UC-human-social Covered PRD Requirements: FR-13, FR-14, FR-15 Cross-Subsystem Rationale: None — single subsystem.

Overview

Makers mark short social posts as human-authored using the same seal family as docs, without depending on platform-preserved file metadata.

Ideal Future State

Operator attaches or includes the H-cue Innsigle mark (image and/or link). Viewers can open a short explanation URL. Unsigned is valid. Mark is not a separate “purity brand.”

Problem Statement

Current situation: Mark SVGs exist; social placement pattern needs productized guidance and walkthrough.
Pain points: C2PA/EXIF die on X-class platforms; human posts need a visible maker-controlled cue.
Desired outcome: Documented social pack + caption pattern + same-family rule.

Requirements

Functional

SOC-01. Human-authored mark asset (H cue) available as SVG/PNG path. SOC-02. Placement pattern does not require surviving C2PA/EXIF on the platform. SOC-03. Pattern includes viewer path to meaning (profile/site/short URL). SOC-04. Per-post signature is optional; unsigned human marks allowed. SOC-05. Social mark uses same seal family as docs (not a fork brand). SOC-06. Issuer identity MUST be publishable without a self-operated webserver: durable HTTPS host for issuer document (gist/Pages/static host) plus issuer card embed on social profiles (fingerprint + absolute keys URL) per ADR-003 D7. SOC-07. Profile embeds are discovery/corroboration only; they MUST NOT be presented as cryptographic seals.

Non-Functional

Caption/template text stays under ~280 chars for X when including URL.
Issuer card fits common bio limits when shortened to fingerprint + keys URL.

Acceptance sketches

ID	Scenario	Expect
SOC-02	Platform strips metadata	Mark still visible as image/link
SOC-05	Compare H and A assets	Shared outer geometry; cue differs
SOC-06	Maker has only GitHub + X	Can publish issuer.json via gist/raw and put card in bio

Dependencies

FEAT-001 seal family
ADR-003 D7 social / profile discovery