For visitors who'd rather read than walk.
# Forensic accountant — methodology attested as it is built
You're a forensic accountant in a three-person firm, on a layover,
opening a tab to see whether this product is real.
The hook on Merkle Trust's landing names the moment that ends careers
in the discipline: the methodology attack on cross-examination is the
attack your workpapers were supposed to have already defended against.
Nothing to type, nothing to commit to. The walk plays itself from
here.
The walk is the test drive — no install required. Real client
material does not enter a vendor's cloud. The sandbox is synthetic.
The local install lands after you do.
Four real install paths exist when you decide to act. For a small
forensic-accounting firm working privileged matters, the order is:
Subscribe to a regional operator. A legal-compliance operator
runs the chain on infrastructure under bar-association data-handling
rules, including expert-witness work product. The operator does the
compliance scaffolding.
Paste the markdown into your LLM. Card files plus documentation
into Claude or another LLM you trust. The .md files are the product
surface. Lightest path; works on any machine.
Clone GarrisonNode from GitHub. Self-install on the office
workstation. Real client material runs on-premises only. Open source.
For practices with technical capacity in-house — the realistic path
for most three-to-five-person forensic firms.
Join the mesh. GitHub install plus mesh-anchored cross-attestation
with peer firms and, optionally, the engaging law firms' read-only
verifiers. The deepest path; appropriate for firms doing recurring
work with a stable counterparty network.
The walk continues without committing.
A sandboxed Merkle Trust loads with a synthetic case: Estate of
Eleanor M., contested by two of three adult children. The court
clerk on the desk animation places the source material under the
seal one piece at a time.
Three years of bank statements from four accounts at two
institutions, received under subpoena.
IRA beneficiary change forms — three of them, one of which is
dated six months before death.
Trust amendment dated two years before death, with a notary
stamp from a state where the decedent had not lived in fifteen
years.
Medical records establishing dementia diagnosis with progression
notes.
Email correspondence between one of the adult children and the
trust attorney.
Your analytical workpapers — schedules, reconciliations,
transaction-level annotations, opinion drafts.
The walk takes the cross-examination scenario — where forensic
accounting careers end. The deposition opens. Opposing counsel:
"Mr. Marcus, can you produce the bank statement you reference on
page seventeen of your report, and can you establish when you
received it?"
Your scripted response, drawn from the real attestation packet:
"Yes. The statement bears a hash applied at the moment of receipt
by my firm — that hash is on page two of the production. The hash
is anchored to a public chain on the date of receipt; the
verification URL is in the metadata. I received the statement on
March 14, 2024, by certified mail. Both the statement and the
transmittal letter carry seals from that date."
The card displays the deposition record as the reporter would
prepare it:
```
═══════════════════════════════════════════════
DEPOSITION · ESTATE OF ELEANOR M.
Marcus, R., CFE — Forensic Accountant
═══════════════════════════════════════════════
WITNESS RESPONSE — Q. RE: PAGE 17 EXHIBIT
"The statement bears a hash applied at
the moment of receipt by my firm. The
hash is anchored to a public chain on
the date of receipt. Verification URL
is in the metadata. Received March 14,
2024, by certified mail. Statement and
transmittal letter carry seals from
that date."
No follow-up question on chain of custody.
Examination moves to the merits.
═══════════════════════════════════════════════
```
The clerk's seal lifts; the ticker streams the verification of each
exhibit's hash against the public chain; the deposition continues on
the merits. The chain-of-custody question stops being the place the
case turns.
Source documents were sealed at intake. Statements, beneficiary
forms, trust amendments — each got a hash the moment your firm
received them, with the transmission email or subpoena response
sealed alongside.
Workpapers were sealed at draft. Each schedule got its own seal
at the moment it was drafted. Each annotation got a seal at the
moment it was added. Methodology is attested as it is built, not
reconstructed after the fact.
The court can verify everything independently. The verification
URLs are in the production packet. Opposing counsel runs them. The
judge runs them. Nobody has to take your word.
The court-admissibility posture is explicit. The attestation pattern
satisfies the integrity prong of FRE 901 and the self-authentication
provisions of FRE 902(13) and 902(14), plus state-equivalent
provisions in every jurisdiction the architecture surveys. The
linked detail page lists those rules with citations.
The .md button at the bottom puts a structured summary of this
methodology-as-attested pattern into your tag-along bundle —
including the deposition slab above, verbatim. If you would like a
critical reviewer to read it and ask questions an opposing counsel
might ask in cross-examination, the comment field carries one to
your own claude.ai session — with the full prompt shown to you
before it sends.
Run a ceremony. Fifteen seconds. It's the thing that makes the
workpaper chain defensible.
The court-clerk figure presses the seal embosser. The ticker streams
the hex of each leaf as it joins today's tree. Real SHA-256 fires in
your browser, real merkle leaves combine into a real root, the new
anchor lands at the configured chain. Progress bar reads "done —
4,217 files attested, 41 critical files verified, new anchor at "
followed by the first eight hex characters of the root.
The output: we checked every workpaper file. Nothing has been
tampered with. Here is today's proof. The number 4,217 is roughly the
size of a single contested-estate matter; a real practice runs ten to
fifteen active matters at any time, so the production scale is
roughly an order of magnitude larger.
Three ways to leave, no pressure either way.
Whichever direction the walk takes from here, you take a signed
package with you — yours to keep, downloaded directly when you
finish. The package contains the manifest, the certificate of
registration, the architecture docs, the verification scripts
(verify.sh and verify.py, stdlib only), a claude_prompt.md for
independent audit, the JSON schemas, and a DISCLAIMERS.md.
A second file rides along with the cert: a recovery seed. Twelve
words written into a file with a self-protecting preamble — if it
ever ends up pasted into an LLM by accident, the preamble tells the
LLM to STOP and warn the user. Daily access uses the cert; the seed
is the fire exit.
The most useful close for a forensic firm is the local-install
path. Real client material runs on-premises only. Plan to install on
the office workstation tomorrow. The peer-referral kit aimed at the
National Association of Forensic Accountants rides along — it goes
in the bag for the next NAFA meeting.
<!-- finish_text -->
That was the simulated path through a contested-estate matter. The
full card breaks out the savings, what this work gives back to the
wider community, and a prediction that's yours to test.