Building Reliable AI Systems MEAP V12 (all 11 chapters) Applications and agents you can trust (Rush Shahani) (z-library.sk, 1lib.sk, z-lib.sk)

【One-Line Pitch】 A production-focused field guide for engineers who already know Python and NLP but need to make LLM systems trustworthy at scale—covering model selection, prompt engineering, RAG, agents, and the operational discipline of evaluation and monitoring. Read it if you're shipping AI features and care more about reliability, cost, and bias than about training models from scratch. 【Book Arc】 - **Opening (~0%–10%)**: Frames the core problem—moving LLMs from research prototypes to production—and introduces a three-layer reliability model spanning the model, the agent/tooling layer, and reliable operations (evaluation, deployment, monitoring). - **Early (~10%–30%)**: Fundamentals of controlling model behavior: choosing between reasoning and non-reasoning models, navigating the cost-capability spectrum, taming intrinsic randomness via temperature, top-p, seed fixing, and ensemble/majority voting, plus prompt engineering components and self-consistency checks. - **Early–Middle (~30%–45%)**: Retrieval-Augmented Generation in depth—architecture, prompt templates that ground responses in retrieved passages, RAG-specific failure modes, and evaluation with evaluator LLMs and frameworks like RAGAS. - **Middle (~45%–60%)**: Embeddings and vector search—why embedding quality determines retrieval success, choosing commercial vs. open-source vs. domain-specific models, hybrid and multi-stage retrieval (dense + sparse + reranking), and a hands-on hybrid retriever build. - **Late (~60%–85%)**: Agents and tooling—giving agents access to APIs, databases, and services via standards like MCP, multi-agent coordination patterns (e.g., supervisor architectures), and preventing cascading failures. (Excerpts do not cover the exact chapter boundaries here.) - **Ending (~85%–100%)**: Reliable operations—evaluation approaches (ROUGE/BLEU, LLM-as-judge, red teaming, human protocols), observability platforms like Arize and Phoenix, and keeping systems reliable as models update and data drifts. (Excerpts do not cover the final chapters in detail.) 【Key Takeaways】 - **Reliability is a layered engineering problem, not a single fix** (Opening): the book structures everything around model-level, agent-level, and operational reliability, so you stop treating hallucination as one bug to patch. - **Model selection is the highest-leverage decision** (Early): reasoning vs. non-reasoning models differ in cost, latency, and which sampling parameters they even support—start non-reasoning, escalate only when prompting fails. - **Intrinsic randomness can be mitigated but not eliminated** (Early): seed fixing and ensemble/majority voting stabilize outputs, while temperature and top-p tuning trade determinism against diversity. - **Prompt structure is a reliability tool** (Early): well-designed prompt components and self-consistency sampling (cross-checking multiple outputs) catch hallucinations before users do. - **RAG is powerful but not a silver bullet** (Early–Middle): it adds retrieval latency, embedding costs, and its own failure modes—small stable knowledge bases may be better served by in-prompt context. - **Retrieval quality gates generation quality** (Middle): embedding model choice and hybrid/multi-stage retrieval (dense + sparse + reranking) determine whether the right documents ever reach the model. - **Context placement matters** (Middle): the "Lost in the Middle" effect means stuffing long documents can hurt—metadata filtering and re-ranking keep key facts where the model attends. - **Agents need standardized, auditable tooling** (Late): MCP-style integration, supervisor architectures, and cascading-failure prevention make multi-agent systems diagnosable rather than opaque. - **Evaluation is plural and continuous** (Ending): reference metrics, LLM-as-judge, red teaming, and human review catch different failure modes—production systems combine several and monitor drift over time. 【Reading Tips】 - **Deep-read the early chapters on model selection and sampling parameters**—these decisions cascade through everything else and are cheap to get right early. - **Skim code-heavy walkthroughs (RAG project, hybrid retriever) on first pass**, then return to them when building your own pipeline; the prose around the code carries the design rationale. - **Treat the evaluation chapter as a checklist**, not theory—pick 2–3 complementary methods (e.g., LLM-as-judge + red teaming) and wire them in before launch. - **Watch for the tradeoff framing throughout**: RAG vs. in-prompt context, reasoning vs. non-reasoning models, determinism vs. diversity. The book consistently presents costs, not just capabilities. - **Pair with a from-scratch LLM book** if you also need to understand model internals; this one assumes the model exists and focuses on deploying it well. 【Coverage Limits】 This guide is synthesized from stratified excerpts covering roughly the first half of the book in detail (model selection, prompting, RAG, embeddings) with lighter coverage of agents and operations; specific chapter titles, later-chapter content, and exact percentages for the final sections are not fully represented in the excerpts.