For visitors who'd rather read than walk.
# Cross-border attorney — three jurisdictions, one chain
You're a cross-border attorney with offices in El Paso and Juárez,
taking thirty minutes between hearings to evaluate something a
colleague mentioned.
The hook on Merkle Trust's landing names what your practice has
always carried alone: the chain of custody across three jurisdictions
is not three chains. It is one chain that the courts on both sides
of the border can verify against the same anchor.
Nothing to type, nothing to commit to. The walk plays itself from
here.
The walk is the test drive — no install required. Real privileged
work runs locally and never in vendor cloud — a posture you expect
after a decade of scrutinizing privilege exposure.
Four real install paths exist when you decide to act. For a binational
practice spanning data-localization-aware jurisdictions, the order is:
Subscribe to a regional operator. A legal-compliance operator
serving cross-border practices runs the operator-side scaffolding.
Each office configures its own attestation surface; the operator
handles the compliance work that varies between jurisdictions. The
path most binational solo practices take.
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 — one node per
office, one attestation chain that spans both. Real privileged work
runs on-premises in the jurisdiction where it belongs. Open source.
Join the mesh. GitHub install plus mesh anchoring. The deepest
path, and the one that fits the binational case the cleanest: the
local rustchain runs in-jurisdiction (the data does not cross the
border), the public anchor preserves only the merkle root (which can
cross every border), and the courts on both sides verify against the
same root.
The chain crosses borders; the data does not have to.
A sandboxed Merkle Trust loads with a synthetic case: Estate of Don
Hernández, lottery winner. The court clerk on the desk animation
places the binational record under the seal — six items, three
jurisdictions, one verifiable chain.
A scanned lottery ticket purchased at a Pronósticos counter in
Tijuana, with an attestation seal applied at the moment your client
photographed it on her phone.
A witness signature added in El Paso, sealed at the moment the
witness signed on a tablet at your office.
A notarized declaration by Don Hernández's daughter in Miami,
sealed at the Florida notary's tablet at the moment of notarization.
Three transmission emails between you, your client, and a
despacho contable in Juárez, each sealed at the moment of receipt.
Two legal opinions — one from a Mexican attorney on Mexican
prize-claim law, one from a Texas attorney on community-property
implications — each sealed at draft completion.
A pending claim filing prepared for the Florida probate court,
ready to ship.
The walk takes the hearing scenario — these cases live or die on
chain-of-custody questions across borders. Opposing counsel:
"Counsel, can you authenticate the lottery ticket photograph? The
witness signature in Texas? The notarization in Florida? Each of
these crossed a border. Who handled them, and when?"
Your scripted response, drawn from the real attestation packet:
"Each item was sealed at the moment of authorship in the
jurisdiction where it was created — the Mexican notario, the Texas
witness, the Florida notary, each generating a seal in their own
legal context. The seals were anchored to a public chain that is
visible from every jurisdiction with internet access. The court
can verify each seal against the same anchor I am verifying
against. The chain crossed the border; the data did not have to."
The card displays the binational record as the court would log it:
```
═══════════════════════════════════════════════
ESTATE OF DON HERNÁNDEZ · BINATIONAL
Tijuana · El Paso · Miami · ONE CHAIN
═══════════════════════════════════════════════
Tijuana ─┐
│
El Paso ─┼──→ Public anchor ──→ Probate court
│ (root only) (any side)
Miami ─┘
Each item: sealed in jurisdiction.
Anchor: visible from any jurisdiction.
Data: stays where it was authored.
Root: verifiable against the same hash
from a court in Mexico, Texas, or
Florida — without contacting the
other offices.
═══════════════════════════════════════════════
```
The clerk's seal lifts on each of the six items; the ticker streams
each verification; the hearing proceeds. The chain-of-custody
question stops being the place the case turns.
Each item was sealed at its origin jurisdiction. The Mexican
notario, the Texas witness, the Florida notary — each generated a
seal at the moment of authorship, in their own legal context.
The seals were anchored to a public chain. The chain is
jurisdiction-independent — a court in Mexico, the United States, or
anywhere else with internet access verifies the same anchor.
Time and place are recorded with the seal. Local timestamp, UTC
timestamp, geographic origin where consented. Time-zone games and
chain-of-custody attacks fail on cryptographic grounds.
The "Anchored here" link resolves to a real receipt: a real merkle
root, a real timestamp, a one-line explanation.
Posture note specific to international practice: the public chain is
selected for global accessibility, not jurisdictional preference.
Where the foreign jurisdiction has data-localization rules, the local
rustchain runs in-jurisdiction and the public anchor preserves only
the merkle root, not any underlying data. The chain crosses borders;
the data does not have to.
The .md button at the bottom puts a structured summary of this
binational chain-of-custody pattern into your tag-along bundle —
including the three-jurisdictions-one-chain slab verbatim. If you
would like a critical reviewer to read it and ask questions a
binational counterparty might ask, 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
binational 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 —
1,219 files attested across two jurisdictions, 18 critical files
verified, new anchor at " followed by the first eight hex characters
of the root.
The output: every file across both your offices is sealed. Nothing
has been altered since the date of seal. Here is today's proof. The
"across two jurisdictions" phrasing is the new note — the ceremony
understands that the practice spans both sides of the border and
treats it as one operational surface.
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 binational practice is the
referral-to-the-binational-bar-association path. The partner kit is
aimed at attorneys with practices on both sides of any border — the
US-Mexico, US-Canada, EU-UK, the binational corridors that run
through every developed legal market. The bar association meeting is
in May. The kit goes in your bag.
<!-- finish_text -->
That was the simulated path through this card. Read the full card
for the soft-sell numbers, the commons benefit, and the
prediction-frame close.