What happened
STRATT had begun building Choco HQ — the enterprise team workspace, the most complex of three planned surfaces — before validating outcome demand via the simpler stratt.works domain portal. The audit work surfaced this as a sequencing flaw: enterprise infrastructure (unit publishing, MERIDIAN live, CRDT real-time, multi-council orchestration) was being built for outcomes that no domain professional had paid for yet.The discovery
When a product family shares one substrate but serves different audiences, the simplest surface validates the underlying value. If domain professionals will not pay for “review this contract” rendered in plain English on stratt.works, no enterprise team is going to pay for the same outcome plus governance, audit, and gates. stratt.works ships in days (Astro + outcome cards + an orchestrator wrapping the existing CLI). Choco HQ ships in months (real-time CRDT, three session modes, plenary war room, audit bridge). The cheap experiment runs first.Why this happens
Engineering bias defaults to “build the most general solution and the simpler ones fall out.” That works for libraries. For products it inverts the right order: demand validation is uncertainty reduction, and you reduce the most uncertainty per dollar at the simplest surface.Pattern to repeat
| Step | Action | Reason |
|---|---|---|
| 1 | Identify the substrate (the protocol / engine that all surfaces share) | The substrate is the asset; surfaces monetise it |
| 2 | List candidate surfaces in order of complexity, ascending | Cost-to-ship is dominated by surface complexity, not substrate |
| 3 | Build the simplest surface first; ship it; measure demand | Cheapest demand-validation experiment |
| 4 | Use the demand signal to fund / cut the larger surfaces | Avoid sunk cost on infrastructure for outcomes nobody buys |