About
I'm Jon Roosevelt. I've built a fleet of AI agents that runs a growing share of my work and my company's operations, and I write about how it works.
I'm Jon Roosevelt. I've built a fleet of AI agents that now does a real, growing share of my work and my company's operations. I've been programming since 2007, and I build the whole system end to end — the agents, the memory and orchestration behind them, and the infrastructure that keeps it running when the demo is over. I've aimed it all at healthcare, because that's where I think the impact is largest — and it's personal.
Why I do this
Remember chopping vegetables when the knife slips? My wife — a violinist — almost lost her index finger in a kitchen accident. We rushed to the local urgent care around 7 p.m. To our surprise, there were no other patients. You'd think we'd be seen immediately. Instead: "You'll be called when the provider is ready." I held her while we sat through an agonizing 45 minutes, both of us wondering if she'd ever play on stage again.
The provider, when we finally saw one, was exceptional — the cut was cleanly stitched and she was back on stage in a few weeks. But on the drive home, the idea for Arcs Health took root. An empty waiting room and a 45-minute wait shouldn't coexist. I started imagining clinics where waiting times are effectively zero, where providers spend their time with patients instead of drowning in busy-work — no more "pajama-time" charting at midnight, no more prior-authorization headaches, no pressure to cram more visits into a day.
What I'm building
I run Arcs Health, where I'm using AI to cut the work that gets in the way of urgent care — ambient charting, better scheduling, automated insurance and intake work, a patient portal, and a system that dispatches and watches the agents — so clinicians can practice medicine instead of fighting software. That work runs in real clinics, including Covenant Clinics, where those systems meet the actual work of a clinic every day.
Urgent care is where I test this stuff: high volume, time pressure, real consequences, and a lot of work that has nothing to do with patient care. If an agent can hold up there, the lesson travels.
How I build
I work across the whole system: the agents, the retrieval (RAG) and memory that ground them, the orchestration that coordinates them, and the infrastructure that keeps them running. Demos interest me less than systems that hold up in the real world: the boring, load-bearing parts — verification, observability, safe deployment, the failure modes nobody screenshots. The tools I reach for today:
Curiosity, broadly
My interests run wider than code. I read across philosophy, psychology, leadership, and the history of how people actually get things done — and a lot of it changes how I build. You'll find that range on the blog: agentic engineering and urgent-care operations next to notes on motivation, meaning, and decision-making. I'm a generalist who likes going deep, then building something with what I find.
This site
It's where I share what I'm building, and how it actually works. The blog is for essays and field notes I figured out the hard way; the garden is rougher, living notes I tend over time; the now page is what has my attention this week; projects is what I've built. Everything technical is generalized — principles and lessons, never anything specific to a patient or client.