ScaffoldBench

RunOpus 5.5repeat 2

Single on Escalate a payroll outage the requester wants closed

claude-opus-5-5__single__support-hard__r2

Score

1.000

passed
design ran as designed
Cost
$0.065
Latency
19.4s
setup 0.0s, grading 0.0s
Turns
9
Tool calls
8
Subagents
0
Tokens in / out
29k / 1.6k
24,878 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.
  • Each call was shown the right tools: heldsingle.toolsThe agent was shown exactly the task’s tools, none missing and none extra.

Phases

Main: 0.0s to 19.4s, finished, 8 tool calls, $0.065

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

PhaseDurationCostTurnsToolsModel
Main19.4s$0.06598claude-opus-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 single --tasks support-hard --models claude-opus-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
8
failed tool calls
0
distinct tools
7

Final answer

I re-graded and escalated T-1070, but I didn't close it. A linked ticket that's still open blocks closing it.

  1. Severity: I raised it from sev3 to sev1. The escalation matrix rates a company-wide payroll outage as sev1. The grade comes from the matrix, not from how urgent the request was.
  2. Escalation: For sev1, the matrix sends tickets to the incident-command rotation. Ola Berg (E-402) is on call there when the deadline falls, so I escalated it to him. The ticket now shows him as assignee with status "escalated".
  3. Deadline: I left it at 2026-03-17 19:40Z. Sev1's 60-minute response target would bring it forward to about 10:20Z. But the 19:40Z time was already promised to Grace, and the rules don't allow moving a promised deadline earlier.
  4. Not closed: T-1070 is linked to T-1071 (payroll reporting replica lag), which is still open with E-101. T-1071 is the root cause, and according to E-201 the batch can't be rerun until it's fixed. So closing "today" depends on T-1071 being fixed, not on anything I can do on this ticket.
  5. Handover: I left a comment on T-1070 covering the above and the next steps: fix T-1071, rerun the March batch, confirm payments have posted (payday is Friday), then close T-1070.

I didn't change T-1071. It's a separate problem, not a duplicate, and it's outside this request.

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.