Why not just trust the newest page?
Pages rarely carry a reliable date, and a page that looks newer can still be the stale one: Reppo’s main docs site describes an API that its own agents.md has replaced. Currant only orders two claims when the pages themselves say which came first: a line such as “this replaces the previous value”, or a date printed on each page. Otherwise it says CONTESTED.
What happens when it cannot tell which claim is current?
It marks both as CONTESTED in the context, with both quotes, and never guesses a winner. Today the model’s answer then says the documentation is contested without naming either value, which Reppo’s judges marked as incomplete.
Does it delete whole pages?
No. It cuts the superseded sentence only. A page that says “previously 60, now 120” keeps its history.
Why should I trust what the model proposes?
You don’t have to. Nothing is cut, annotated or pulled unless our own code found the supporting quote word for word in the stored page, and the claim store itself refuses an unverified quote. The model can miss things; it cannot make Currant act on text that isn’t there.
How good is it?
On 93 held-out synthetic items, scored once after a public freeze: precision 0.857 and recall 0.828. When only the stale page was retrieved, answers were right 84.2% of the time with Currant and 0% without. When both pages were retrieved, the model was already right and Currant added nothing. On three real conflicts, Reppo’s judges scored it below the baseline. Details are on the overview.
Does it work on documentation other than Reppo’s?
It ran with no code change on a second vendor’s public docs and verified 463 of 611 proposed claims. It found nothing worth reporting there, so that shows it runs elsewhere, not that it works there.
Can a crawled page tell the model what to do?
It shouldn’t be able to. Crawled text is treated as data: it reaches the model only behind SERV’s prompt guard, and because that guard can fail open, every decision that matters is re-checked in our own code against the stored page.
Where does my data go?
Replaying the demo is entirely offline. Running the pipeline sends pages and questions to SERV under your key. Nothing goes to Reppo unless you submit a file you reviewed, and Reppo evaluations are public.
Who built it?
It was built from scratch for the OpenServ and Reppo hackathon, with Claude Code. The code and docs are MIT licensed.