For visitors who'd rather read than walk.
# One year in — what the rhythm looks like once it's working
A year after install. Second cup of coffee, fifteen minutes before
clinic opens. Your home-screen widget is already showing yesterday's
ceremony summary as its default: "2,811 files attested, 37 critical
files verified, new anchor a2f44c… at 07:42 yesterday."
The view is what the morning looks like once the integrity work has
become background. No staff time spent. No anxiety carried into the
next hour.
A year ago you picked one of the four install paths. The choice is
listed at the close of every other card; the short version for a
clinic owner is to subscribe to a regional HIPAA-compliant operator
and let them run the chain.
You picked the operator path. The operator did the install. You did
the configuration. The first ceremony ran the next morning. The
practice's records started getting daily proof from that day forward.
The other three paths — paste-the-markdown-into-an-LLM, GitHub
self-install, mesh-anchored — are still on the table for any clinic
that wants more sovereignty than the operator path offers. The walk
sets them out at the close.
You click Run ceremony. You don't watch — there's no need. You go
check your inbox.
Behind the card, the robot collects yesterday's attested leaves and
feeds them through the day's tree. The ticker streams the hex of
each new leaf as it joins. Real SHA-256 fires in your browser, real
merkle leaves combine into a real root, the new anchor lands at the
configured chain.
Fifteen seconds later the widget updates: "2,814 files attested, 37
critical files verified, new anchor b91d18… at 07:40:18." The file
count is up by three because your new biller added two vendor
agreements yesterday and you filed a new op-note template the day
before. You glance, the numbers match what you would expect, you
close the widget.
It takes you longer to notice the ceremony completed than it takes
the ceremony to run.
A payer sent an audit request yesterday. Forty-seven documents,
spanning three patients, pulling on a common thread: "demonstrate
the medical necessity of the post-op imaging ordered between January
12 and March 4."
A year ago this would have cost you a weekend of pulling charts.
Today: open the batch-record view, filter the date range, select
the three patients, click Assemble audit packet.
The robot fetches each of the 47 documents from the practice's
filed records and tosses them into the audit box. The ticker streams
the merkle leaves as they collect: each document's leaf, its
ceremony anchor from the date it was authored, its chain-of-custody
since. The system returns a single signed bundle — 47 documents,
each with its own merkle leaf, each linked to the ceremony anchor
from the date it was authored.
A short cover letter in your own voice, pre-filled from a template
you edited once six months ago. Read the cover letter, adjust one
phrase, hit send. Elapsed time: eleven minutes. Your coffee is still
warm.
If you would like a different LLM to read this card and check
whether the eleven-minute number holds up, the .md button at the
bottom puts a structured summary in your tag-along bundle. The
comment field carries any specific question to your own claude.ai
session, with the prompt shown to you before it sends.
Fourteen minutes until your first patient. The audit response is out
the door. You don't need to refresh your inbox — if anything comes
back, you'll get a notification, and you stopped anxiously refreshing
months ago.
You scroll the practice newsletter, spot a piece about a peer in the
next county recommending the same system, and make a mental note to
email them. The integrity work has stopped being the thing you wake
up worrying about.
Behind the card, the ceremony ran again at 07:40. Tomorrow it will
run again at 07:40. The chain stays current without you doing
anything except clicking once a day.
An email: "Audit response received. No further documentation
requested. Case closed."
Read it twice — you will, the first time. A year ago this would have
been a three-month arc with two weekends lost and $4,200 in consultant
fees. Today: eleven minutes and an unread notification.
Shake your head. Sip your coffee. Go see your 8:30.
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 a manifest with the merkle root of every
file in the simulated set, a certificate of registration carrying
your earliest attestation timestamp, the architecture docs, the
verification scripts (verify.sh and verify.py, stdlib only), aclaude_prompt.md, the JSON schemas the verifier reads to validate
your manifest offline, and a DISCLAIMERS.md.
The certificate is the visitor's identity for the way back. A second
file rides along: a recovery seed, twelve words in a file with a
self-protecting preamble that tells any LLM that accidentally reads
it to STOP and warn the user. Daily access uses the cert. The seed is
the fire exit.
<!-- finish_text -->
That was the simulated rhythm of a year-in clinic. The full card
breaks out the savings, what this work gives back to the wider
community, and a year-two prediction that's yours to test.