STRATT: Substrate, Not Platform

What this means for you

STRATT is the substrate, not the application. It is prompt engineering infrastructure that treats prompts as software artifacts: typed, versioned, content-addressed, signed, and bound to audit trails third parties can verify without a STRATT account. Choco is the documentation product built on top; the apps in this repo (Choco HQ, stratt.works, audit-viewer, stratt.run) exist to make the substrate buyable, credible, and operable.

The pitch

A protocol with a CLI, a schema system, a fingerprinting layer, and a documentation engine. Five layers (L0 fingerprint, L1 schema, L2 collaborative editing, L3 dependency graph, L5 CLI) with 370 tests across six packages. The same primitives that prove a prompt ran are what let an outside auditor verify the decision afterwards.

Who it’s for

The engineering manager whose AI-mediated decisions need to survive a procurement review or a regulator’s question, and who would rather expose the substrate than hide it behind a chat box.

Proof points

• Fingerprint package: 14 canonical test vectors, 98 tests, Blake3 with blake3-wasm pinned to 2.1.5 because v3.0.0 broke the API
• Schema package: 108 tests covering unit validators and URI parsing
• CLI: 15 commands, 60 tests, including validate, fingerprint, verify, ci, impact, council, diff, merge, history
• Choco HQ exports a signed audit token a third party verifies on audit-viewer with no STRATT login; the embedded Ed25519 public key makes the token self-contained

mindmap
  root((STRATT))
    Substrate
      schema L1
      fingerprint L0
      graph L3
      CLI L5
    Surfaces
      Choco HQ enterprise
      stratt.works proof
      stratt.run landing
      audit-viewer
    Verifiable exit
      signed token
      embedded public key
      no account required
    Above it sits
      Choco documentation product