A synthetic matter, run through the real engine: three accounts over three months, from three declared sources — a bank subpoena production, the client, and the subject — plus a ledger export and a payment-app export. Every figure in it is made up; every check on it is the one a real matter gets.
One bound PDF, indexed and paginated, with the method version, the engine line and the findings hash on the cover. Its sections, in order:
The Excel schedule carries the same page citations as section 9, one row per transaction, with a link that opens the source file at the cited page when the schedule sits in the folder with the files. Download the sample schedule.
The proof block on the cover: how many statements read tie to their own printed closing balance, and how many carry notes a reviewer has to resolve. Section 2 shows the balance chain per account and names the first month that does not chain with its neighbour. Section 8 lists every authenticity note with what it means and what to verify — it never says what a note proves. Section 11 says what was not checked.
The subject's own statements in this sample carry notes weighted high. The bank's subpoena production is not weighed at all: source decides how the authenticity section is read, and the reviewer declares the source.
Download the sample matter's files, drop them into a free matter in the order the README gives, and compare the findings hash on screen with the one on the exhibit's cover. The same files, the same method version and the same edits produce the same hash on any build. The procedure for a real matter.