Skip to main content

​
The Insight

Most platforms try to serve every audience with one interface. The interface tries to be everything — outcome-friendly enough for the lawyer, technical enough for the operator, governable enough for the enterprise — and ends up too complicated for the lawyer, too simple for the operator, and too opaque for the enterprise. STRATT solves this by treating the protocol as the asset and shipping three separate surfaces that each speak the right language to one audience. One engineering investment. Three sellable products. Zero compromise on vocabulary.

​
The Three Surfaces

SurfaceAudienceWhat they see
stratt.worksDomain professional (lawyer, analyst)Outcome cards: “Review a contract.” “Run due diligence.” Plain English, zero protocol vocabulary.
Choco HQEnterprise teamUnit library, fingerprints, gates, plenary war room, workflow pipeline. The protocol is first-class.
RockyInternal builderFull operational cockpit: CRDT queues, blast radius, vault, deployment. Stays internal.
A signed audit bridge lets external stakeholders verify Choco HQ session decisions without ever touching Rocky.

​
The Architectural Discipline

Three layers of machine-enforced separation keep the surfaces from collapsing into each other:
  1. A single chokepoint package translates outcome-level calls into protocol-level calls and returns redacted DTOs. Protocol fields cannot leak through a sanctioned channel.
  2. A static boundary check in CI blocks any forbidden import from the outcome-only surface. Protocol packages cannot leak through a casual import.
  3. A DOM-purity Playwright spec crawls every public route and asserts forbidden tokens never reach the rendered HTML. Protocol vocabulary cannot leak through a hard-coded string.
Each layer catches a different failure mode. Together they make leakage a class of bug that does not ship.

​
Why It Matters

A product family built this way can be priced and sold separately. The lawyer pays per outcome. The enterprise pays per seat with a governance package. The internal builder is a cost centre that produces the engine. One protocol, three economic models, zero feature compromise.

​
The Cryptographic Bonus

Audit tokens issued by Choco HQ are Ed25519-signed over canonical JSON, with the public key embedded in the token itself. Any third party can verify the audit trail without contacting STRATT — handed to a regulator, an opposing counsel, or a customer’s compliance team, the artefact stands on its own. This is what compliance-grade attestation looks like when you build the protocol first and the surfaces second.