Dokki: a RAG pipeline in three planes
Documents in, grounded answers with sources out — split into a data, control, and query plane on the existing MJTHD stack.
WRITING
Build logs, post-mortems, and notes worth keeping. Newest first.
Documents in, grounded answers with sources out — split into a data, control, and query plane on the existing MJTHD stack.
Minimum Viable Product, properly understood: not half a solution, but the fastest experiment to learn something real.
Immutable versions, snapshots as a manifest, and rollback as a mere pointer flip — how Dokki protects the production corpus.
A design process in four phases — and why most of the work happens before the first solution idea.
A two-stage check before every promotion — a cheap sanity check, then an eval set against the active snapshot. Activation only at equal or better quality.
How Dokki turns a question into top-k chunks of the active snapshot — HNSW on halfvec, a shared embedding model, and sources you can look up.
Turning off the data collection that ships on by default — in dev, in CI, and in the image.
The deploy pipeline behind this page: build once, sync from git, route two domains to one service.
Why this site exists, and what you'll find here.