The Website Is the Proof

What this means for you

Choco does not launch with a hero video. It launches with a working surface that proves the claim. The website is built on the platform; the changelog is a published doc; the code samples on the homepage execute. An evaluator who view-sources the page sees the same attestation chain that customer docs carry.

The pitch

Phase one is the brand surface itself. Phase two is the authoring loop: a developer runs choco init, ships a doc, and watches the verifier render the attestation inline. Phase three is the proof reaching its audience: evaluators land on choco.tools, understand the category in thirty seconds, and leave with a one-line summary they can paste into Slack.

Who it’s for

The advisor or peer asking how choco intends to convert evaluator visits into adoption without the usual devtools template.

Proof points

• Brand surface and product app are the same Next.js application; every change to cho-co-web is a change to choco’s own published record (cho-co/web/PRODUCT.md § Product Purpose)
• Evaluator success criterion is timed and named: thirty seconds to understand the category, three minutes to a confident judgment, a one-line Slack summary on exit (choco-design-system/PRODUCT.md)
• Author success criterion is timed and named: a choco init command they trust, then a flow from blank doc to attested page that never blocks on a save dialog or merge-conflict modal
• The active execution roadmap sequences five blocks before public launch (web hardening, contracts, gateway, auth, document engine) per ROADMAP.md § Block A through Block F

timeline
  title Choco launch path
  Phase 1 : Brand surface ships : choco.tools served by cho-co-web
  Phase 2 : Authoring loop : choco init to attested page
  Phase 3 : Evaluator landing : 30 seconds to category, 3 minutes to judgment
  Phase 4 : First external customer site : same pipeline as choco.tools
  Phase 5 : Reader trust : verification chain rendered on every doc