Verifiable Docs, Not a Wiki and Not an LLM Wrapper

What this means for you

Choco is a documentation platform where every published page carries a cryptographic record of who wrote it, when it shipped, and which code samples were executed and passed. If you have ever cited a doc that was quietly wrong, choco is the version of that doc you could have trusted on first read.

The pitch

Authors write in the factory. The compiler verifies the prose, runs the code samples, and the TimeChain ledger attests the result. Readers see the attestation chain rendered next to the page, not claimed in a footer. The website that ships choco is itself served by choco, from the same pipeline customers use.

Who it’s for

The engineer between a stack trace and a deadline who needs the right answer on first read, and the staff engineer who has to pick a docs platform their team will not regret in two years.

Proof points

• The brand surface choco.tools is dog-fooded: served by the live web client from the same compiler and verifier pipeline customers ship docs through, per choco-design-system/PRODUCT.md
• Every primary brand surface has a stable URL and works under curl; SPA-only routing for primary content is forbidden, so agentic clients reach the surface as easily as humans do
• Three distinct first-class audiences are named in the product register: doc authors, doc readers, and evaluators, each with a separate workflow on the same outward surface
• Apache-2.0 open core; the docs body type and the authoring surface share the same ink budget so that long-form reading is never an afterthought

mindmap
  root((Choco))
    Verifiable
      compiler runs samples
      attestation rendered
    Editorial
      document as artifact
      durable not feed
    Addressable
      stable URLs
      curl reachable
    Dog-fooded
      choco.tools is choco
      website is the proof