Choco HQ: The Enterprise Surface for STRATT

What this means for you

Choco HQ is the enterprise workspace for teams running AI-mediated deliberations they intend to defend afterwards. It speaks the protocol natively (councils, gates, signed audit tokens) because its readers are engineering managers and staff engineers who will read a unit URI to disambiguate. The same deliberation can be exported as a token an outside counsel or regulator verifies without ever logging in.

The pitch

A council workspace where every gate, override, and adjudication writes to a signed ledger before the UI fires. Three session modes (plenary, chamber, pipeline) for the three shapes of decision. One signed audit token, self-contained public key, third-party verification with no STRATT account required.

Who it’s for

The engineering manager whose AI deliberations have to survive a procurement review or a regulator’s question, and who wants the substrate exposed rather than hidden behind a chat box.

Proof points

• Plenary, chamber, and pipeline session modes shipped under /sessions; the three deliberation shapes are routes, not modal dialogs
• Audit token route /audit/[token] sits outside the auth boundary by design; the embedded Ed25519 public key means verification needs no STRATT infrastructure
• Override justifications shorter than 20 characters throw OverrideRejectedError at the orchestrator boundary, before the UI notification fires
• Built on @stratt/orchestrator, @stratt/fingerprint (Blake3, 14 canonical test vectors), and @stratt/signature; the same substrate the third-party audit-viewer reads

mindmap
  root((Choco HQ))
    Native protocol
      councils
      gates
      unit URIs
    Three session modes
      plenary
      chamber
      pipeline
    Verifiable exit
      signed token
      embedded public key
      no login required
    Substrate exposed
      ledger before UI
      Blake3 fingerprints
      override threshold