Proof & Trust

Module 3 was about not shipping something false. This is about being able to show your work in a way that survives someone checking it.

Those are different problems. The first is a check you run before a piece goes out. The second is what you can put in front of a stranger who has no reason to believe you, and it has to be built while you work — you cannot assemble it afterwards from memory.

1What this module is not

It is not a promise that this works.

There is a version of this module that shows you screenshots of view counts and tells you what other creators earned. That version would be easy to write and you should distrust every guide that contains one — including this one, if it did.

We cannot show you proof that you will get results, because that evidence does not exist yet and it will not belong to us when it does. It will belong to your clients. §1 is about what follows from that, and it is more useful than a promise would have been.

2What's in here

3The one idea

4Where the mechanics already live

Two things in this guide already do this discipline rather than describe it, and this module points at them instead of re-explaining:

• claim-guard (Module 2's skills folder) runs the mechanical version — tracing every claim to a source before anything ships. Module 3 §3 teaches the discipline it automates.
• The sales page's memo demonstrates the pattern for handling illustrative material honestly: a stated exception, labelled where the reader meets it, rather than a distinction they have to infer.

Both are worth looking at as worked examples. Neither is repeated here.