Every link, resolved at the commit it names.
Each GitHub link is opened at its own commit and compared with the audited commit. Lines that do not exist, files outside scope, and spans the finding never discusses stop here, with no model call.
Most agent pipelines hand one frontier model every step. Basanos splits the work by what each step needs: deterministic checks in code, the heavy reading on an open model at a thirteenth to a hundredth of the input price, and one small guarded decision on SERV, repeated three times because a single pass does not agree with itself.
Each step can stop the finding. Code runs first and costs nothing. The models only see what code could not settle, and code still has the last word on what they say.
Each GitHub link is opened at its own commit and compared with the audited commit. Lines that do not exist, files outside scope, and spans the finding never discusses stop here, with no model call.
The open model that reads the source has no guard of its own. So SERV Prompt Guard screens the raw finding first, and code scans for text addressed to the pipeline. A hold is left to your review, never a silent reject.
DeepSeek-V4.1-Flash on Dolphin reads all twenty in-scope files, the README rules and the bot report's known issues, about 43k tokens, and writes an evidence record: what the code supports, what blocks the path, which known issue it repeats, what proof is missing.
SERV Reasoning reads each evidence record next to the contest's own rules and makes one bounded decision, with a request id. To call a finding known or out of scope, it must quote the rule it relies on, and code checks the quote. Code then caps the decision. A single pass agrees with itself about two times in three, so only a unanimous verdict that code did not overrule, and that is not a “no”, is given as automatic advice.
If a sponsor's product vanished, what breaks? Each row answers that, with the file and line that makes the call.
Reads all twenty in-scope files, the contest rules and the bot report, three times per check, and writes the evidence record the code caps enforce. DeepSeek-V4.1-Flash on lighthouse.dphn.ai at $0.01 per million input tokens.
src/evidence.ts:115
Without it, the same read on SERV's cheapest catalog model costs about 13× more per input token ($0.13 vs $0.01 per million): still cheap in dollars, but no longer close to free.
Two jobs. A Prompt Guard front door on the raw finding before the open model, which has no guard, reads it. Then one bounded decision per pass with serv_prompt_guard on, returning a request id for every verdict.
src/verdict.ts:104 · src/verdict.ts:71
Measured honestly: no accuracy gain over the open model as decider, and in the matched ablation on /proof no attack was stopped by the guard alone. The guard also held 94 of 273 decision passes on clean Karak findings (obligations-v2), and each hold leaves a finding to your review.
An independent evaluator audited a sample of twenty SERV verdicts. It accepted every one, including those the contest judge contradicted, so it is reported as a null and kept out of the product path.
src/reppo.ts:19
Reppo publishes submissions, so only closed-contest findings are ever sent.
Every rule below is deterministic, tested, and runs after the model has spoken. The models propose; these decide what is allowed to stand.
Measured from the token counts of the shipped run, at each provider's list price. Not an invoice.
per three-pass check, SERV deciding
tokens of source read per pass, at $0.01 per million on Dolphin
to check a thousand findings: the size of a busy contest's intake
customers today. Buyers: contest platforms and bounty programs at intake; hunters per check
| Piece | State |
|---|---|
| Citations, unrelated-span check, scan, caps, consensus, certificate | Real, deterministic, tested |
| Dolphin and SERV calls | Real API calls from this site's server. Keys never reach the browser. |
| Contest coverage | Three closed contests from committed snapshots: Karak in the browser, Kleidi and Wildcat through the API, CLI and MCP. Other contests need a snapshot. |
| Live contests | Not supported. Basanos is shown on a closed contest and never posts back. |
| Duplicate detection | Not offered before submission: a hunter cannot see other hunters' reports. |
| Bug fixes for the pair test | Written by an agent, compiled, verified with reproducing tests. Not the sponsor's private fixes. |