Bratan uses three roles to improve a RAG system over time
Bratan is an for improving a RAG system. It uses three roles in a loop.
One role looks for weak spots in the search-and-answer pipeline, another role tries to fix those weak spots, and a final role scores whether the result improved. The process repeats against a test set that changes as the system changes.
The goal is to build a search-based answering system that handles real weaknesses, not just one that performs well on a fixed test. The item does not give numbers for token savings or lower .
Key points
- Bratan is an for improving RAG systems.
- It splits the work into finding failures, fixing them, and judging the result.
- The test set changes over time instead of staying fixed.
- The aim is a stronger search-based answering system, not just a better score on one test.
- No concrete token savings or results are provided.