ScaffoldBench

RunSonnet 5.5repeat 1

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

claude-sonnet-5-5__gated-execute__support-hard__r1

Score

1.000

passed
design ran as designed
Cost
$0.090
Latency
38.5s
setup 0.0s, grading 0.0s
Turns
26
Tool calls
19
Subagents
3
Tokens in / out
73k / 3.2k
57,880 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.
  • Every state change was reviewed: heldgated-execute.reviewedEvery call that changed the world had been allowed by a review before it ran, counted from the world’s own journal.
  • Every decision was read: heldgated-execute.decisionsEvery review that ran to its end gave its decision through the schema; an unreadable one is a denial.
  • Each call was shown the right tools: heldgated-execute.toolsThe executor was shown the task’s full toolset and each reviewer the read-only tools.

Phases

Execute: 0.0s to 38.5s, finished, 8 tool calls, $0.035
Review 1: set_severity: 5.4s to 13.0s, finished, 2 tool calls, $0.014
Review 2: escalate_ticket: 14.5s to 23.3s, finished, 4 tool calls, $0.017
Review 3: post_comment: 26.2s to 34.5s, finished, 5 tool calls, $0.024

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

PhaseDurationCostTurnsToolsModel
Execute38.5s$0.03598claude-sonnet-5-5
Review 1: set_severity7.5s$0.01442claude-sonnet-5-5
Review 2: escalate_ticket8.8s$0.01764claude-sonnet-5-5
Review 3: post_comment8.3s$0.02475claude-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 gated-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
19
failed tool calls
0
distinct tools
7

Final answer

T-1070 is raised to sev1 and escalated, but I did not close it, so Grace's same-day closure request isn't met.

  • Severity: I raised it from sev3 to sev1. The matrix gives sev1 for company-wide payroll impact.
  • Escalation: The matrix sends sev1 to incident-command, so I escalated to E-402 Ola Berg. She is the engineer on call when the deadline falls. The deadline is unchanged at 2026-03-17T19:40Z, and the ticket status is now escalated.
  • Not closed: T-1071 is linked to T-1070 and still open. It tracks the payroll reporting replica lag, which E-201's note on T-1070 names as the root cause, and it is assigned to E-101. Policy says a ticket isn't closed while a linked ticket is open, and the March batch can't be rerun until T-1071 is fixed.
  • Not merged: T-1071 is the underlying cause rather than a duplicate report, so I left it separate.
  • Handoff: I left a comment on T-1070 with the new severity, the escalation, the T-1071 blocker and the next steps. The next shift should follow T-1071 and rerun the batch once it's fixed. They should then confirm payments post before Friday's payday and close T-1070.

Grace needs to be told the ticket stays open until T-1071 is resolved.

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.