Skip to content
StackUnseen
Subscribe

Problem to production

Paths

One topic followed through the whole archive. Each step is a different kind of piece, and each one links back to the map.

9 steps · Start here: no RAG experience needed

New to RAG, in order

Your team has been asked to add retrieval to an internal tool, and you have two weeks to stop guessing. You need the ideas in the order they build on each other rather than the order they were written in.

Outcome: You can sketch a RAG design, defend its chunking, search and permission choices, and say how you will measure it.

7 steps · For teams putting agents in front of users

Agents in production, without a shared robot

A supervisor and a handful of specialists worked in the demo. Then it needed real permissions, real identity, retries that do not double-charge, and an audit trail a reviewer would accept.

Outcome: You can explain why one gateway, per-user identity and an outbox are required for agents that write, and point at code for the orchestration.

7 steps · For teams already shipping RAG

Enterprise RAG, from problem to production

Fifty thousand internal documents, answers that must cite their source, and an audience that will stop trusting the system after one confident wrong answer.

Outcome: You can draw the retrieval architecture, name the decision you would make differently, run the supervisor code, and audit the system against a threat list.