RAGForge / docs /SOURCES.md
ArchitSharma's picture
Upgrade RAGForge to v1.7 evaluation correctness and adaptive efficiency
03bed0b
|
Raw
History Blame Contribute Delete
4.38 kB

Reference projects and implementation sources

No tutorial source code is copied into RAGForge. The requested projects were used as architectural inspiration/checklists.

Requested reference projects

  1. Krish Naik β€” Enterprise Advanced RAG with Hybrid Search, Reranking, HyDE, CRAG, Self-RAG, Text2SQL, Caching and Guardrails in LangGraph
    https://www.krishnaik.in/project/enterprise-advanced-rag-with-hybrid-search-reranking-hyde-crag-self-rag-text2sql-caching-and-guardrails-in-langgraph
  2. Krish Naik β€” Production Grade Cyclic RAG with LangGraph, GCP and Groq
    https://www.krishnaik.in/project/production-grade-cyclic-rag-with-langgraph-gcp-and-groq
  3. Krish Naik β€” Building a RAG-Based Document Search Application
    https://www.krishnaik.in/project/building-a-rag-based-document-search-application
  4. Krish Naik β€” Air India RAG Chatbot Development
    https://www.krishnaik.in/project/air-india-rag-chatbot-development
  5. Educative β€” Building a Retrieval-Augmented Generation System Using FastAPI
    https://www.educative.io/projects/building-a-retrieval-augmented-generation-system-using-fastapi
  6. ByteByteAI β€” AI Engineering curriculum / Ask-the-Web modules
    https://bytebyteai.com/c/ai-engineering

Official implementation references

Evaluation references

v1.5 evidence-driven runtime policy

The adaptive reranker policy and incremental evaluation design are internal engineering decisions informed by RAGForge's own transparent bundled benchmark. They are not presented as universal claims that reranking is ineffective or that one evaluation design is optimal for every corpus. The explicit reranker ablation remains available so the decision can be revisited when corpus size/difficulty changes.

v1.6 evaluation-driven policy

Insight synthesis, hard-mode benchmark cases, table citation semantics, chunk-level reranker labels, profile comparison and evaluation-history deltas are RAGForge-specific engineering additions derived from the project's own observed evaluation gaps. They are not claims that one routing taxonomy or benchmark design is universally optimal.

v1.7 evaluation-policy note

v1.7 does not add a new external dependency or benchmark dataset. The new policies are derived from RAGForge's own auditable v1.6 run data: perfect source/chunk ablation quality with large reranker latency, a false-negative missing-answer case, and Markdown citation-coverage artifacts.