I'm Jon Roosevelt. I run urgent care clinics, and I build the AI agents that do a growing share of the work of running them. I've been programming since 2007. I build the whole system: the agents, the memory and orchestration behind them, and the machines that keep them running after the demo ends.
Why urgent care
My wife is a violinist. A kitchen knife slipped and nearly took her index finger. We got to the local urgent care around 7 p.m. The waiting room was empty. We still sat for 45 minutes before anyone saw her, wondering whether she would play again.
The provider was good. The cut was stitched cleanly and she was back on stage in a few weeks. On the drive home I kept turning over the same fact: an empty waiting room and a 45-minute wait should not be able to coexist. Arcs Health came out of that drive.
What I run
I run Arcs Health. It builds the software that removes the work between a clinician and a patient: ambient charting, scheduling, insurance eligibility and intake, a patient portal, and a system that dispatches and watches the agents doing the back-office work. It runs in real clinics, including Covenant Clinics, where every one of those systems meets the actual day.
Urgent care is a hard test. High volume, time pressure, real consequences, and a lot of work that has nothing to do with patient care. If an agent holds up there, the lesson travels.
I also make Tutti, a bilingual way into classical music that tells you what to listen for instead of what to know.
How I build
I care less about demos than about the parts nobody screenshots: verification, observability, safe deployment, and the failure modes that show up at 2 a.m. Most of what I write here is about those parts. The tools I reach for:
| Tool | Where it sits |
|---|---|
| TypeScript | Default for everything, including one-off scripts |
| Python | Machine learning and data work |
| Astro | This site |
| React | The clinic apps |
| Claude | The model behind the agent fleet |
| Whisper | Speech to text |
| LightRAG | Graph retrieval over my notes |
| Postgres with pgvector | Retrieval store |
| Neo4j | Knowledge graphs |
| tmux | Where the agents live |
| Obsidian | The second brain the agents read from |
| Cloudflare | Pages, DNS, and Workers |
| GitHub Actions | Every deploy |
| Docker | Everything that has to run somewhere else |
Off the clock
I read philosophy, psychology, leadership, and the history of how people actually got things done. Some of it changes how I build, so some of it ends up on the blog next to the engineering.
This site
The blog is where the finished writing goes. The garden holds notes I am still editing. The now page is what has my attention this month. Projects is what I've shipped, and how I run it is the map of the agent fleet and how it got built. Everything technical is generalized: principles and lessons, never anything specific to a patient or a client.
The site is static Astro on Cloudflare Pages. Posts are markdown files in a git repository. A fleet of coding agents helps build and publish it, and the site is honest about how that fleet works and how it fails.