LLM Arbiter Pattern Ranks RAG Retrieval Candidates

A single LLM call ranks retrieval candidates with written reasons, outputting a typed JSON object an auditor can defend. The arbiter pattern sits at the end of a three-stage detection pipeline: keyword and embedding detectors propose, the arbiter decides. A deterministic dispatcher selects which detectors run per question.