Three Users, One Job-to-be-Done
stratt beginner 4 min read
What this means for you
STRATT serves three archetypes, and every design decision starts by answering which one is on the screen. The protocol builder maintains the substrate. The domain professional consumes outcomes on stratt.works and never sees protocol vocabulary. The enterprise team runs deliberations in Choco HQ and reads unit URIs to disambiguate. All three share one job: stake a real engineering decision on a versioned, content-addressed, council-deliberated artifact and prove later exactly what was decided, by whom, against which inputs.
The pitch
The three surfaces are not three products; they are three reading levels of the same protocol. Outcome cards on stratt.works, native protocol vocabulary in Choco HQ, cryptographic detail on audit-viewer. A signed audit token travels from the deepest reader to the outermost without passing through a login.
Who it’s for
The product manager or designer choosing where a feature lives, and the buyer trying to understand why the same vendor ships an outcome surface, an enterprise workspace, and a public read-only audit page.
Proof points
stratt.worksis governed by a DOM-purity test: nostrat://, noblake3:, nofingerprint, noCRDT, nounitas a noun in the rendered HTML- Choco HQ runs three session modes (plenary, chamber, pipeline) for the three shapes of deliberation
audit-viewertargets WCAG 2.2 AAA contrast and a zero-JavaScript reading path, because it gets read on a 7-year-old laptop in adversarial contextsFingerprintBadgeacceptssurface: "pro" | "enterprise"and renders nothing on the pro surface; the same component crosses the boundary without leaking vocabulary
journey title One audit token, three readers section Domain professional (stratt.works) Reads outcome card: 5: User B Sees no protocol vocabulary: 5: User B section Enterprise team (Choco HQ) Runs council, resolves gates: 5: User C Exports signed audit token: 5: User C section Outside counsel or regulator (audit-viewer) Pastes token, reads ledger slice: 5: Third party Verifies without STRATT login: 5: Third partyneighbors on the map
- Engineer-to-Engineer Voice, with a Banlist drafting any copy that will appear on a STRATT-owned surface
- Practice What You Preach: stratt.run as Its Own Audit explaining why stratt.run looks like a document and not a landing page