<#6931 docs: add RAG / LLM failure-mode checklist ...
# flyte-github
a
#6931 docs: add RAG / LLM failure-mode checklist tutorial Pull request opened by onestardao ## Tracking issue Related to #6930 ## Why are the changes needed? RAG / LLM workloads on Flyte are becoming more common, but when a pipeline misbehaves it is still hard for users to reason about where the failure comes from (ingestion, embeddings, retriever, LLM, evaluation, etc.). This PR adds a pointer to a concrete, MIT-licensed failure-mode checklist that: • organizes 16 common failure modes across the main stages of a RAG / LLM pipeline • is already referenced by external projects (e.g. ToolUniverse from Harvard MIMS Lab, QCRI LLM Lab’s Multimodal RAG Survey, and Rankify from the University of Innsbruck) as a debugging / evaluation aid • can serve as a lightweight starting point for Flyte users who are building similar workflows and need a structured way to debug them ## What changes were proposed in this pull request? • Add a “RAG / LLM pipeline failure mode checklist” entry to the Tutorials section of the
README.md
. • The link points to the WFGY ProblemMap page, which documents a 16-problem checklist for RAG / LLM pipelines (covering data ingestion and chunking, embeddings and vector stores, retrievers and ranking, LLM routing / tools, and evaluation / guardrails). This is intentionally a minimal docs-only change. As a follow-up, I am interested in contributing one or two Flyte 2.0 examples that use this checklist to structure RAG / LLM workflows, based on the suggestions in #6930. ## How was this patch tested? • Rendered the README using GitHub’s preview to verify: • the new tutorial entry renders consistently with existing links • the link target is correct and reachable • No code or configuration changes were made, so no unit or integration tests were added. ### Labels • added: new documentation link / tutorial entry ### Setup process Not applicable – docs-only change. ### Screenshots Not applicable – README text-only change. ## Check all the applicable boxes • I updated the documentation accordingly. • All new and existing tests passed. • All commits are signed-off. ## Related PRs None. ## Docs link Not applicable – change is in the main
README.md
only. flyteorg/flyte