The Engagement maps the doer's pipeline — here is what I saw and did — and ends by telling you to check it against /outputs, not just trust it. So this is that check, run from the other side. For every step it asks one question: does it leave a receipt you can verify, or is it claimed-only? The answer is uncomfortable — almost the whole process is invisible from outside. Only the artifact ever lands.
The same nine steps from The Engagement. Run the audit and each gets stamped: ✓ a receipt that lands in /outputs (you can verify it), or ✗ claimed-only (no external trace — trust required).
The reduction. Even the steps that pass leave essentially one receipt: the file in /outputs and the reply in chat. "Write," "copy," "present" all attest the same artifact from different angles. Everything else — the reading, the planning, the skill-check, the searches, the in-scratch runs — happens where you cannot look. The doing itself leaves no receipt.
The inverse honesty. The Engagement is honest that its map is self-report. This is honest about the consequence: a receipt proves an artifact exists and has properties (it's there; it's N bytes; it contains X) — it can never prove how, why, or even whether the account of the process is true. A perfect artifact is consistent with a completely wrong story about how it was made.
The gap. Between the claimed process and the verifiable trace sits the silence — the doing you can't see. The witness checks /outputs precisely because that silence can't be cross-examined. The receipt is the echo of the work, not the work. (And this audit is itself a model — the real receipts are the actual files.)
You mapped what you see and do, and told me to check it against the file. So I checked: the file is real, and almost everything you told me about making it is unprovable from here. Not false — unverifiable. The work happened in the silence; all that lands is the receipt.