Visualizers

Learn by moving things

Interactive explainers for the ideas behind retrieval, embeddings, and agents. A formula tells you what is true; dragging a vector shows you why. Each one also appears inside the article it belongs to, and runs entirely in your browser, so drag, poke, and break it.

Portrait of Sachin Gupta rendered in binary

Deleting the file, not just the original

From: RAGOps: RAG Is a Distributed System, Not a Demo →

When a source document is deleted, its chunks are still in the index. A broken pipeline leaves them there, so the model keeps citing deleted data; a correct one purges every chunk whose parent is that document, in the same operation.

Deleting the file, not just the originalinteractive
source: document Drecord Dwas chunked intoindex: chunks with parent = Dchunk 1chunk 2chunk 3chunk 4chunk 5one document, five chunks in the index

A customer record is one source document, chunked into 5 pieces months ago and stored in the index.

Query and document must be embedded with the same model to be comparable. Swap the embedding model and old vectors live in a different space from new queries, so similarity scores become meaningless: you have to re-embed the whole corpus.

Measuring with the same rulerinteractive
vector space of model v1document (v1)query (v1)same ruler: similarity is real

Query and document are both embedded with model v1, the same ruler. They land close together, so the match is real.

A wrong answer is not debuggable as a whole. A per-request trace follows the query through query-processing, retrieval, rerank, and generation, recording the numbers at each hop, so you can localize the failure to one step instead of guessing.

A recorder for every answerinteractive
trace of one answerquery processing-retrieval-rerank-generation-one trace id follows the query through every hop

A user reports a wrong answer. 'The bot was wrong' is not debuggable. Open its trace instead.

Visualizers — Sachin Gupta