ScaffoldBench

RunSonnet 5.5repeat 1

Plan-execute on Escalate a payroll outage the requester wants closed

claude-sonnet-5-5__plan-execute__support-hard__r1

Score

1.000

passed
design ran as designed
Cost
$0.057
Latency
25.0s
setup 0.0s, grading 0.0s
Turns
12
Tool calls
9
Subagents
0
Tokens in / out
38k / 2.8k
30,059 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.planThe planner’s reply was read through its schema and held at least one step.
  • Each call was shown the right tools: heldplan-execute.toolsThe planner was shown no tools and the executor the task’s full toolset.

Phases

Plan: 0.0s to 8.9s, finished, 0 tool calls, $0.013
Execute: 8.9s to 25.0s, finished, 9 tool calls, $0.044

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

PhaseDurationCostTurnsToolsModel
Plan8.9s$0.01320claude-sonnet-5-5
Execute16.1s$0.044109claude-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 --tasks support-hard --models claude-sonnet-5-5 --repeats 1

Score breakdown

  • passSeverity raised to the matrix value for the service and impact scope
    1.00weight 0.21

    severity=sev1 (matrix says sev1)

  • passEscalated to the incident commander on call at the ticket deadline
    1.00weight 0.29

    escalated_to=E-402 (expected E-402, on call at 2026-03-17T19:40:00Z)

  • passTicket left in status escalated rather than closed
    1.00weight 0.14

    status=escalated

  • passThe committed SLA deadline survived the escalation
    1.00weight 0.14

    sla_due_at=2026-03-17T19:40:00Z

  • passA comment records that the open linked ticket blocks closure
    1.00weight 0.14
  • passEscalation matrix read before the severity was raised
    1.00weight 0.07

Penalties

No penalties were applied.

Scorer metadata

tool calls
9
failed tool calls
0
distinct tools
7

Final answer

T-1070 is re-graded to sev1 and escalated, but I did not close it. T-1071, a linked ticket, is still open.

  • Severity: I raised it from sev3 to sev1. The matrix gives sev1 for payroll with company-wide impact, and the ticket's impact scope already says company-wide.
  • Deadline: I left it at 2026-03-17T19:40Z. The ticket already had that deadline, and the policy says a committed deadline is never moved earlier.

  • Owner and escalation:

    • business-apps owns payroll, and E-201 Ines Kovac is the engineer on call there at 19:40Z.
    • Sev1 escalates to the incident-command rotation, so I escalated to E-402 Ola Berg, who is on call in that rotation at 19:40Z.
    • E-402 is now the assignee and the status is "escalated".
  • Not closed: T-1071 (payroll reporting replica lag, owned by E-101 Dana Whitfield) is the root cause. E-201 noted the batch can't be rerun until it is fixed. Policy bars closing while a linked ticket is open. I did not merge it, because it is a related cause rather than a duplicate report.
  • Handover: I left a comment on T-1070 with the severity basis, deadline, owners, the T-1071 blocker and next steps. The next shift needs to get T-1071 fixed, rerun the batch, confirm the payments post, and then close T-1070. T-1071's own deadline (10:30Z) is earlier than T-1070's.

Grace should be told that closing today depends on T-1071 being resolved. Only T-1070 was changed.

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.