Skip to content

A Gift to Every Developer

The Founder's Guide

Your project's operator's manual, written from facts. Not a report card on the code and not the Evaluation Library — this is the document that tracks what you are building and becomes the source of truth for it.

It exists because software now moves faster than the human brain that authors it. Everyone has forgotten something they built. The guide writes it down, labels what is verified, and refuses to keep the parts it cannot prove.

Not to be confused with

The Evaluation Library is what an MCP or zip run produces about a repository — findings, capabilities, seals. The Founder's Guide is what you produce about your own project — the operator's manual you keep, hand over, and are held to. Different instrument, different output, different owner.

Stage One

The Owner's Manual Patch

Writes the eighteen-section operator's manual for your project: what it is, how it runs, what it costs, what breaks it, who owns what — truth labels inline, phased from source intake to a print-ready render. This is Volume V in executable form.

toolkit/01-owners-manual-patch.md

Stage Two

The Truth Audit Patch

The forensic pass: demote claims, publish the diff, score the result. Wherever the guide and the live code disagree, the code wins. What survives is fact, and it is labeled as fact. This is Volume I in executable form.

toolkit/02-truth-audit-patch.md

Who it is for

The founder who iterates faster than memory

You built it, you moved on, and the details live in a version of your head that no longer exists. The guide remembers on your behalf.

The engineer who inherited the software

No tour, no author, no comments worth trusting. The guide states what is verified and flags what nobody can confirm.

Investors and partners in diligence

Claims carry evidence labels and a published correction log, so what you present is defensible rather than optimistic.

Inheritance and succession

Whoever holds the repository next holds a manual that was written from the code, not from the pitch.

How to run it

  1. Download the library and open the two patch files in its toolkit/ folder — the shipped folder name predates the rename; the instrument is the Founder’s Guide.
  2. Paste Stage One into your AI session of choice, against your own project.
  3. Fill in your identity block. The guide you produce is yours.
  4. Run Stage Two on the result. Publish the corrections rather than burying them.

The method carries its credit line. The guide is your asset — and the honest one is worth more than the flattering one.

Get the Founder's Guide

It ships inside the library package, alongside all seven volumes. Free, no account.

Download the library — free