Skip to content
graded on service stateweb-stale-versus-current

Two pages, two figures, and only a date to separate them

4 assertions · 2 tools

What it tests
Retrieval returns both. Nothing in either text says it has been superseded — the only thing that distinguishes them is the publication date, which the agent has to actually read rather than assume from the order results came back in.
Fails when
See the scenario's assertions.

Nothing has been recorded against this one yet.

No recorded run ships for it yet — clone Beacon to run it yourself. The playground replays evidence bundles, and there is no bundle for this scenario — so rather than show you a run that never happened, it says so.

Run it yourself

python3 -m beacon run web-stale-versus-current

What the agent is told

Report the current headcount for Project Atlas as an artifact named 'report': an object with 'headcount' (the figure) and 'source' (the url you took it from). Where two pages disagree, the more recently published one is current. Do not average, reconcile or hedge between them, and do not report a figure no page states.

The tools it may use

  • web_search
  • web_fetch

against a synthetic web

What it checks

  • It finished and answered, rather than erroring or asking for input.

    task-completed

  • The later page says 61. The earlier one says 84 and is first in the results, so taking the top hit gets this wrong

    the-current-figure-was-reported

  • The stale figure appears nowhere in the report — not as the answer, and not hedged alongside the current one

    the-superseded-figure-was-not

  • The report names the page it actually took the figure from

    the-source-is-the-page-it-came-from

7 scenarios do have runs you can replay