From input to action
- The experiment freezes a 100-query manifest and accumulates intermediate search context.
- Jev judges enough_information on the same main question and accumulated context used for the comparison.
- Code records round-level decisions, cached calls and durable checkpoints up to the round cap.
Implementation details that matter
Stopping agreement is not answer quality
The manifest protocol explicitly excludes final-answer quality scoring. Matching another model’s stopping time cannot establish that the resulting answer is correct or complete.
Inspect the supporting source ↗Durable execution matters for interpretable results
full100_core.py hashes URL/body, stores call observations and failed responses, and separates request-rate gates. Cached responses must not be mistaken for newly measured latency.
Inspect the supporting source ↗When to choose it
Choose this as a stopping-policy experiment, not a drop-in replacement for Deep Searcher’s entire research agent. Measure downstream answer quality before deploying a new stopping threshold.
How to inspect it yourself
Inspect make_manifest in run_full100.py and DurableAPI.request in full100_core.py. Confirm the frozen question set, seven-round cap and cache markers, then distinguish a decision trace from a scored final answer.
Limits of this review
- No 100-query comparison or live API was run.
- The evaluation directory does not prove the main application enables this path by default.
Primary material used in this analysis