Build in volume. Verify everything. Own it all.
Every claim ships with the instrument that produced it. A number without its source is a rumour, and the more fluent a claim sounds the more it needs its receipt.
- The Brief
Most practices carry institutional memory as a vibe. Optimization claims decay, monthly decks cannot be reproduced a quarter later, and the green checkmark nobody has ever seen fail proves nothing.
- Diagnosis
Make verification structural rather than aspirational. Gates fail closed and get broken on purpose once so red has been seen. Records append rather than rewrite. Disagreement between two sources becomes a tagging convention rather than a judgement call.
- The Build
01 · Every claim ships with its instrument
A live fetch for factual claims, a command for deliverable claims, the actual artifact for anything contested. A zero result is a claim too - it must name the scope that produced it before it can be reported.
02 · Gates fail closed, and every gate has been watched failing
The deploy gate refuses a dirty tree. The document factory deletes any PDF that leaks a placeholder. Scripts that can spend money refuse to run un-armed. Each was broken deliberately once to watch it go red.
03 · When two sources disagree, instrument the disagreement
An API provably blind to what an interface shows became a tagging convention - every finding labelled by which instrument saw it. Epistemics as file format rather than as vigilance.
04 · Rent commodity substrate, own product logic and data
Hosting and payment rails are swappable commodities. The CMS, the CRM modules, the datasets, the engines and the document factory are owned outright - which is why every case in this register ends with the client owning something.
- Artifacts Delivered
- 01Maintained inventory of every deployed build, with what each one taught
- 02Production URLs gated against the hosting platform’s ownership registry
- 03Fail-closed gates on deploys, documents and spend
- 04Append-only, dated records across every engagement
- Outcome
A verified working record that compounds: build volume produces public proof, proof anchors the pitch, engagements run on the verification discipline, and the discipline produces the records that become the next case.
- Receipts
- 256dated builds charted from the inventory; 258 live per the platform API
- +95builds shipped in a single month, January 2026
- 440days of working record, excavated on demand rather than recalled
- Not yet known
- —Revenue attributable per build
- —Which lessons changed which outcomes
- —Cost of the verification discipline itself
The inventory records what each build taught but not what each build earned, and the two have never been joined. The discipline’s own overhead - hours spent checking rather than shipping - is likewise unmeasured. Both are answerable; neither has been asked.
"Tools are rentable and templates are copyable. A verified record of building, checking and owning is neither."