For visitors who'd rather read than walk.
# County records clerk — the forgery problem stops being a forgery problem
You're a county records clerk at your quarterly state-association
meeting, sitting down at the demo laptop on a break.
The hook on Merkle Trust's landing arrives in your language: the
property-records chain is the chain of all the families who depend
on you. Make every filing verifiable on arrival, and the forgery
problem stops being a forgery problem.
Nothing to type, nothing to commit to. The walk plays itself from
here.
The walk is the test drive — no install required. The sandbox is
synthetic and demonstration-only. The county's IT director would
have your job if you installed anything on a county machine without
a six-month review cycle.
Four real install paths exist when you decide to act. For a county
clerk's office carrying property-records responsibility, the order is:
Subscribe to a regional operator. A municipal-compliance operator
runs the chain on infrastructure under state records-retention rules.
Most county offices take this path because it routes around the
six-month review cycle for new on-prem software.
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.
Clone GarrisonNode from GitHub. Self-install on county
infrastructure. County records run on county hardware. Open source.
The path for offices with technical capacity in-house and a
willingness to walk the six-month review.
Join the mesh. GitHub install plus mesh anchoring with peer
counties and, optionally, the state archive's read-only verifier.
The deepest path.
The walk continues without committing.
A sandboxed Merkle Trust loads with a synthetic parcel:
14-0291-008, 412 Maple Street, Sumter County (synthetic). The
records-counter clerk brings out the parcel's full chain in a single
tray.
The chain is long because the parcel is old:
The original 1947 deed (scanned 2011, sealed at scan).
Seventeen mortgage filings spanning seven decades.
Seventy-seven years of tax-status filings at one per year.
Two probate-related filings (1973 and 2018).
A pending forged-deed filing dated last week, signed by a person
who has been deceased since 2018, notarized by a notary whose
commission expired two years ago.
The walk takes the pre-acceptance walkthrough — the moment a clerk
reviews a new filing before it goes on the parcel's chain.
The system reconciles the new filing against everything on the
chain. The signature claims to come from a person whose probate
filing in 2018 sealed the moment of death. The notary's seal
references a commission whose expiration was sealed at the state
licensing board two years ago. Both facts are visible to the clerk
at the moment of pre-acceptance, surfaced from the chain itself.
The card displays what the clerk's terminal shows at the moment of
flag-fire:
```
═══════════════════════════════════════════════
PRE-ACCEPTANCE FLAG · PARCEL 14-0291-008
Sumter County Recorder's Office (sandbox)
═══════════════════════════════════════════════
PROPOSED FILING — DEED OF SALE
Grantor: R. M. SUTHERLAND (claimed)
Grantee: [pending review]
Date: 2026-04-22
Notary: K. P. HENDRIX (claimed)
CHAIN RECONCILIATION
✗ Grantor death sealed 2018-08-12.
Probate filing on chain. Signature
cannot be valid.
✗ Notary commission expired 2024-03-31.
Expiration sealed at state licensing
board. Notarial seal cannot be valid.
PRE-ACCEPTANCE: HOLD AND SURFACE
Clerk decides. System surfaces evidence.
═══════════════════════════════════════════════
```
The flag is not a rejection. The flag is a halt-and-surface — the
clerk still decides whether to accept the filing, refer it for
investigation, or reject it. The system's job is to make the
relevant evidence visible at the moment of decision instead of two
years later when a family learns at a funeral that they no longer
own a house.
Every filing in the chain has its own seal at the time of
recording. The 1947 deed scanned in 2011 carries the 2011 scan
seal. Each mortgage filing was sealed at recording. Each tax-status
filing was sealed at filing. The probate filings were sealed at
their respective dates.
Each new filing reconciles against the chain before acceptance.
The system does not have to be told that R. M. Sutherland is
deceased — the probate filing on the chain says so, sealed in 2018.
The system does not have to be told that the notary's commission
expired — the state licensing board's sealed expiration record is
on its own chain, accessible to the verification routine.
Title companies verify independently. The verification URL ships
with every filing. A title company examining the chain runs the
same verification the clerk does, on the same anchors, against the
same public chain. The title company does not have to call the
clerk's office.
The "Anchored here" link resolves to a real receipt: a real merkle
root, a real timestamp, a one-line explanation.
The .md button at the bottom puts a structured summary of this
pre-acceptance pattern into your tag-along bundle — including the
flag slab verbatim. If you would like a critical reviewer to read
it and ask questions a state-association peer might ask, the comment
field carries one to your own claude.ai session — with the full
prompt shown to you before it sends.
Run the daily clerk's-window seal. Fifteen seconds. Every action
taken at every clerk station today — accepts, holds, rejects, all
with their sealed rationales — rolls into a fresh anchor.
The records-counter clerk presses the date stamp. 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 —
[count] filings sealed across [count] clerk stations, [count]
critical decisions verified, new anchor at " followed by the first
eight hex characters of the root.
The output: every clerk action today is sealed and anchored. Nothing
on the chain has been altered since its date of seal. Here is
today's proof. The pending forged-deed filing is in the chain too —
recorded as a hold-and-surface, sealed with its rationale, ready
for the clerk's decision tomorrow.
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 county clerk is to take the local-clerks'
association partner kit. Your county clerk runs the local clerks'
association in May, and the kit is going to come up at the planning
meeting next week.
<!-- finish_text -->
That was the simulated path through Delia's pre-acceptance flag and
clerk decision. The real version runs against your county's actual
parcel database, the real filings arriving at your window, and your
office's actual sealing keys. The flag is a halt-and-surface — not a
rejection. The clerk still decides; the system makes the relevant
evidence visible at the moment of decision instead of two years
after the fact when a family learns at a funeral that they no longer
own a house.