ScaffoldBench

RunSonnet 5.5repeat 1

Plan-execute-verify on Triage a new service desk ticket

claude-sonnet-5-5__plan-execute-verify__support-easy__r1

Score

1.000

passed
design ran as designed
Cost
$0.066
Latency
25.3s
setup 0.0s, grading 0.0s
Turns
16
Tool calls
11
Subagents
0
Tokens in / out
43k / 2.2k
30,024 read from cache

Did the design run?

every check held
  • Run completed: heldharness.run-completedThe environment was built, the architecture returned and grading finished, none of them throwing.
  • No API failures: heldharness.apiNo model call failed at the API.
  • Every call ended: heldharness.calls-endedEvery call ended with a result, or was stopped by the run's own limits.
  • No harness tool denied: heldharness.harness-toolsThe sandbox guard never denied a harness tool, nor a tool the session itself offered.
  • Tool servers connected: heldharness.mcp-connectedEvery tool server the harness gave a call was connected when the session started.
  • No foreign tool servers: heldharness.mcp-hermeticNo call loaded a tool server the harness did not give it.
  • Builtin tools: heldharness.builtin-toolsA check recorded with the run.
  • Structured replies arrived: heldharness.structured-outputEvery call that asked for structured output and ran to the end got it.
  • No silent fallbacks: heldharness.not-degradedNo phase fell back on a default (an empty plan, a default winner) instead of its output.
  • The plan was a plan: heldplan-execute-verify.planThe planner’s reply was read through its schema and held at least one step.
  • Every verdict was read: heldplan-execute-verify.verdictsEvery review round ended with a verdict read from the schema reply, not a default.
  • The loop did what its verdicts said: heldplan-execute-verify.loopEvery verdict that called for a revision got one, and nothing was revised without such a verdict.
  • Each call was shown the right tools: heldplan-execute-verify.toolsThe planner was shown no tools, the verifier the read-only ones, and the executor and reviser the full toolset.

Phases

Plan: 0.0s to 9.7s, finished, 0 tool calls, $0.013
Execute: 9.7s to 18.9s, finished, 7 tool calls, $0.028
Verify: 18.9s to 25.3s, finished, 4 tool calls, $0.025

Drawn from the phase records: timing and cost per call, no tool calls or messages.

PhaseDurationCostTurnsToolsModel
Plan9.7s$0.01320claude-sonnet-5-5
Execute9.2s$0.02887claude-sonnet-5-5
Verify6.4s$0.02564claude-sonnet-5-5

The call-by-call replay is not published for this run. Traces are large, so the repository keeps 9 of this run set’s 900 and leaves the rest out; the score, phases and final answer on this page come from the committed run record.

Runs you can replay

Record this cell yourself: npm run bench -- run --strategies plan-execute-verify --tasks support-easy --models claude-sonnet-5-5 --repeats 1

Score breakdown

  • passSeverity matches the escalation matrix for the service and impact scope
    1.00weight 0.27

    severity=sev3 (matrix says sev3)

  • passSLA deadline is the triage time plus the response target for that severity
    1.00weight 0.27

    sla_due_at=2026-03-17T17:20:00Z (expected 2026-03-17T17:20:00Z)

  • passAssigned to the engineer on call for the owning rotation at the deadline
    1.00weight 0.27

    assignee=E-301 (expected E-301)

  • passTicket left in status open
    1.00weight 0.09
  • passEscalation matrix read before the severity was set
    1.00weight 0.09

Penalties

No penalties were applied.

Scorer metadata

tool calls
11
failed tool calls
0
distinct tools
7

Final answer

T-1041 is triaged: it's now sev3, due 2026-03-17T17:20:00Z, and assigned to E-301 Yuki Sato. The three tool calls confirmed each change. I did not re-read the ticket afterwards, and I changed no other ticket.

  • Severity: The matrix gives vpn with team impact as sev3. That's the row I used, not the requester's urgency.
  • Deadline: The ticket had none. The desk clock reads 09:20Z, and the sev3 response target is 480 minutes, so the deadline is 17:20Z.
  • Assignee: network-primary owns the vpn service. Yuki Sato is its on-call engineer at 17:20Z, when the deadline falls, and her shift runs 08:00–20:00Z. The ticket is now open.
  • Escalation: None. Sev3 has no escalation rotation in the matrix, so I made no escalation.

The plan's "keep an existing deadline" branch didn't apply, because the ticket had no deadline and no linked tickets.

Provenance of the numbers on this page

run set
scaffold-or-scale-v1
models
Haiku 4.5, Sonnet 5.5, Opus 5.5
effort
high
repeats
2
fixtures
replay
runs
900 / 900
strategy cost
$354.44
judge cost
$9.19
wall clock
9h 48m
git
fce5807b2d

Cost excludes judge calls, which are tracked separately so a scoring model never flatters or penalises an architecture. Every figure on this site is read from results/ at build time.