03Requirements
Answer questions over supplied documents with traceable citations. Unsupported questions should produce a clear decline instead of an invented answer.
OPENING THE SYSTEM
Loading the next page…
Loading the next page…
A document search and question-answering service that retrieves permitted source material, ranks relevant passages and returns cited answers or declines when evidence is insufficient.
An end-to-end RAG pipeline ingests documents, persists local embeddings in ChromaDB, combines BM25 and semantic retrieval, reranks the candidates and generates cited answers with Groq. Weak evidence triggers abstention.
Document question answering needs to find relevant evidence and recognise when the available context cannot support an answer.
Load documents, split them into chunks and preserve source metadata for later citations.
Answer questions over supplied documents with traceable citations. Unsupported questions should produce a clear decline instead of an invented answer.
Load documents, split them into chunks and preserve source metadata for later citations.
Combining keyword and semantic relevance while enforcing document access, then separating retrieval failures from unsupported answers during evaluation.
Document ingestion, chunking, local embeddings and persistent ChromaDB storage form the knowledge layer. Source metadata travels with retrieved chunks.
BM25 complements semantic retrieval for exact terminology. Reciprocal-rank fusion merges the ranked lists; a cross-encoder then reranks the candidate evidence.
Groq generates answers from retrieved context. Citation validation and confidence-based abstention make evidence and uncertainty part of the output contract.
FastAPI exposes typed query contracts, health and readiness checks, authentication, document access controls and structured request logs. Document permissions are checked during retrieval and again before generation. Per-user rate limits use an in-memory limiter within one process. Docker packages the service.
A 50-case golden-set workflow separates retrieval, answer quality and abstention checks. Unit and regression tests cover API permissions, citation behaviour and failure paths. The full answer-quality evaluation requires configured model access; the workflow itself is not a completed accuracy benchmark.
Keep ingestion, retrieval, reranking and generation separate so each stage can be inspected and evaluated. Treat refusal to answer as a valid outcome when the evidence is weak.
Expand representative evaluation cases, measure retrieval and answer quality together, and document latency, cost and failure behaviour under realistic workloads.