Three Readers, One Substrate

What this means for you

STRATT serves three reader archetypes, and each one has its own surface. Choco HQ is for the enterprise team that speaks the protocol. The professional consuming finished work goes to a different surface where protocol vocabulary is forbidden in the DOM. The third-party verifier reads a stripped-down audit page. Knowing which reader is on screen is the question that comes before any design decision.

The pitch

User C (enterprise team) lives in Choco HQ and reads gates, blast radius, and unit URIs without translation. User B (domain professional) lives in stratt.works and never sees a fingerprint string. The third-party verifier (outside counsel, regulator) lives in audit-viewer and never logs in. One protocol, three audiences, three surfaces.

Who it’s for

Anyone briefing a page or component for the STRATT product family who needs to choose between exposing the substrate and hiding it.

Proof points

• Three archetypes named in PRODUCT.md: protocol builder (Rocky), domain professional (stratt.works), enterprise team (Choco HQ / meridian)
• DOM-purity Playwright spec rejects any leak of strat://, blake3:, fingerprint, blast-radius, CRDT, or unit (as noun) on the stratt.works surface
• Choco HQ ships FingerprintBadge and TypeBadge components on screen; the same components carry a surface="pro" prop that renders nothing when a User-B page mounts them
• audit-viewer targets WCAG 2.2 AAA contrast and a zero-JavaScript-required reading path, because its reader may be on a 7-year-old laptop behind a corporate proxy

quadrantChart
  title STRATT readers, by protocol fluency and depth
  x-axis "Skim" --> "Deep read"
  y-axis "Protocol invisible" --> "Protocol native"
  quadrant-1 "Enterprise team (Choco HQ)"
  quadrant-2 "Domain professional (stratt.works)"
  quadrant-3 "Drive-by visitor"
  quadrant-4 "Third-party verifier (audit-viewer)"
  "Enterprise team": [0.9, 0.95]
  "Domain professional": [0.7, 0.1]
  "Third-party verifier": [0.85, 0.55]
  "Procurement evaluator": [0.4, 0.4]