For visitors who'd rather read than walk.
# Independent pharmacist — chain of custody and the recall that didn't take seventy-two hours
You're an independent pharmacist with a small herbal-medicines line.
Quiet thirty minutes between consults. You're looking for a tool
that would have made the last recall scare easier — the one where it
took the supplier seventy-two hours to confirm which lots were
clear and which were not, and where every patient call you fielded
during that window cost you trust you spent years building.
Merkle Trust's landing names the feeling. Nothing to type, nothing
to commit to. The walk plays itself from here; you watch.
The walk is the test drive — no install required.
Four real install paths exist when you decide to act. For an
independent pharmacy, the realistic order is:
Subscribe to a regional operator. A pharmacy-compliant operator
runs the chain. The grower, the cooperative, the transport carrier,
the contract lab — each can configure their own attestation surfaces
on their own schedule. The operator handles the cross-entity
scaffolding without forcing the supply chain onto a shared software
stack. The path most independent pharmacies take.
Paste the markdown into your LLM. Card files plus documentation
into Claude or another LLM you trust. Lightest path; works on the
back-office Mac.
Clone GarrisonNode from GitHub. Self-install on the back-office
machine. The install lands behind the dispensing terminal, not on
it. Open source. For pharmacies with technical capacity in-house.
Join the mesh. GitHub install plus mesh anchoring. The deepest
path, useful for multi-store independents and pharmacy cooperatives.
The walk continues without committing to a path; the close lists all
four again.
A sandboxed Merkle Trust loads, pre-populated with a synthetic batch
of valerian root. The record shows seven attestations along the
chain.
Grower attestation from a field at Cooperative Green Hollow:
field ID, harvest date, moisture content at bale, grower signature.
Cooperative aggregation attestation: batch ID, gross weight,
visual inspection photo, aggregator signature.
Transport attestation: temperature-logged transit, vehicle ID,
driver signature.
Pharmacy receiving attestation: your signature, date, weight
reconciliation.
HPLC constituent profile with peaks, dates, instrument ID,
operator.
Contract lab certificate of analysis (CoA): heavy metals panel
(Pb, As, Cd, Hg all within spec), pesticide panel (clean), microbial
panel (clean).
Release to retail: your signature, retail lot number, bottle
count.
The walk takes the recall path — that's the one that keeps a
pharmacist up at night. The walkthrough loads a synthetic scenario:
a contaminant is discovered in a sister batch from the same field.
The robot pulls every attestation from the affected field's chain
and tosses them into the recall box. The ticker streams the merkle
leaves as the graph traversal runs.
Seven seconds later: every bottle from the affected field is
highlighted across the simulated retail shelf. Every practitioner
who dispensed a bottle from that batch is listed. Every patient
record that references the batch is flagged for outreach. A recall
letter is pre-drafted, populated with the batch ID, the field, the
test result, and the recommended action.
That would have been seventy-two hours and a legal panel.
The "Show me what just happened" panel breaks it down in plain
English.
Every attestation in that chain is hashed. A hash is a
fingerprint — change one field and the fingerprint changes. Change
one attestation and the chain breaks.
The chain is anchored. The anchor is verifiable without calling
us. A patient, a practitioner, a state inspector, or a plaintiff's
attorney can check the chain themselves. The "Anchored here" link
opens a real receipt: timestamp, merkle root, one line explaining
each.
The recall query is just a graph walk. The system knows which
bottle came from which batch came from which field came from which
grower. Any node queried returns the subgraph in milliseconds.
The word "merkle" may be new — the receipt explains itself by the
time you reach the bottom.
The .md button at the bottom puts a structured summary of the
chain-of-custody pattern into your tag-along bundle. If you would
like to ask a state-board-style question and read a critical
response, the comment field carries one to your own claude.ai session
— with the full prompt shown to you before it sends.
Before the walk goes further, run a ceremony. It takes 15 seconds
and it's the thing that makes the chain defensible.
The robot collects the day's attestations from across the chain. 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. The panel
reads: "every batch record, every attestation, every test result
re-verified. Nothing has been tampered with. Here is today's proof"
— with a link to the full merkle tree receipt.
Other parties in the chain — the cooperative, the contract lab, the
imaging center analog — run their own ceremonies on their own
schedules. Their proofs link to your packet through cryptography,
not through any shared system you have to trust.
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 carrying your earliest attestation timestamp, the
architecture docs, the verification scripts (verify.sh andverify.py), 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 a
visitor accidentally pastes it into an LLM, 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 pharmacist is the share-with-someone
path. The state-association compounding committee head needs the
explainer; the cooperative growers need the explainer; the contract
lab benefits from the explainer. The kit is one page each, written
for the audience that will actually read it.
<!-- 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.