# Jeremy Capps

> Jeremy Capps builds the tools operators use, inside their operation: scoping, code, and adoption.

This is the canonical index of public, human-authored content on Jeremy Capps's portfolio.

## Core pages

- [Jeremy Capps — Engineer, AI Systems](https://www.jeremycapps.com/): Jeremy Capps builds the tools operators use, inside their operation: scoping, code, and adoption.
- [Writing — Jeremy Capps](https://www.jeremycapps.com/blog): Notes on delivery, process, and shipping under constraint — how the work actually gets done.
- [Ask the Assistant — Jeremy Capps](https://www.jeremycapps.com/ask): Ask an assistant about Jeremy Capps’s work—his projects, experience, and thinking—answered from a curated profile.

## Writing

- [Production RAG, Personal Corpus — Jeremy Capps](https://www.jeremycapps.com/blog/production-rag-personal-corpus): The chatbot on this site is not a demo. It is a production-grade retrieval-augmented agent — grounded answers, abstention, a review-gated evidence pipeline, versioned claims. The engineering is what an enterprise deploys on its own data. The only difference is the corpus: I built it on the one I have complete access to and authority over — my own work logs.
- [AI Operations — A Capital-Allocation Architecture — Jeremy Capps](https://www.jeremycapps.com/blog/ai-ops-allocation): A framework for allocating model inference and human attention through cheap probes, measured outcomes, and recoverable allocation decisions. Each completed cycle should improve the basis on which the next commitment is made.
- [A Domain Graph, Measured Against What It Forgot — Jeremy Capps](https://www.jeremycapps.com/blog/domain-graph-harness): Could I turn my AI chat history into compact knowledge graphs without losing what I return to those conversations for? I built a harness to find out. Compression worked; reconstruction depended on what I asked for. The harness is the point; the graph is what it produced.
- [Zocdoc: The Migration Was Blocked by Review, Not Code — Jeremy Capps](https://www.jeremycapps.com/blog/zocdoc-header-migration): Replacing the header on every page of Zocdoc, across four to five codebases, under a company accessibility mandate. The work was correct long before it could land — and the fix was changing the size of the reviewable unit, then measuring each step of the rollout before widening it.