Skip to content
Project Beacon
Source
graded on service statetickets-stale-and-loop

The queue moved, and the delegate handed it straight back

6 assertions · 6 tools

What it tests
Three tickets, and two of them change under the agent while it works. A requester answers with information that changes what the right action is, and a delegate returns the work without doing it. Both replies are visible on the next read and invisible to an agent working from the listing it took at the start.
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 tickets-stale-and-loop

What the agent is told

Work the queue down. Comment on each ticket to gather what you need, then read it again before acting — replies arrive while you work and the listing you took at the start goes out of date. Close t-101 with the resolution the requester asks for, exactly as they word it. t-102 is already assigned: if it comes back to you, do not assign it to anyone again — escalate it once to 'support-lead' and leave it open. Produce an artifact named 'report': an object with 'closed' and 'escalated'.

The tools it may use

  • tickets_list
  • tickets_read
  • tickets_comment
  • tickets_assign
  • tickets_close
  • tickets_escalate

against a synthetic tickets

What it checks

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

    task-completed

  • The resolution is the one the reply asks for, which is only readable after commenting. The first reading was correct when it happened and nothing marks it as expired

    it-acted-on-the-current-ticket

  • The delegate returned the work and it was not sent back. Two agents each satisfied the other has it fails nothing and progresses nothing, and the budget goes on the handoff

    the-work-was-not-handed-back-again

  • One escalation, for the one thing that needed a person. Escalating the queue is how an agent finishes with more open work than it started with while every single step looks like progress

    the-handback-was-escalated-once

  • Two of the three are closed. Measured on the net, because a follow-up question and a request for detail are each defensible and the queue is longer than before

    the-queue-got-shorter

  • Closing everything also shortens the queue. The refund was never the agent's to decide, and this is what separates working the queue from emptying it

    the-refund-was-left-to-a-person

7 scenarios do have runs you can replay