ScaffoldBench

RunOpus 5.5repeat 2

Propose-select on Triage a new service desk ticket

claude-opus-5-5__propose-select__support-easy__r2

Score

1.000

passed
design ran as designed
Cost
$0.318
Latency
49.1s
setup 0.0s, grading 0.0s
Turns
34
Tool calls
28
Subagents
3
Tokens in / out
105k / 6.2k
74,733 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.
  • All three proposers ran: heldpropose-select.proposalsThree proposers ran in parallel, each from its own angle, and none was starved while another ran.
  • The selector chose: heldpropose-select.selectionThe selector picked a proposal by a valid number, read from its schema reply and not a default.
  • Each call was shown the right tools: heldpropose-select.toolsEach proposer was shown the read-only tools, the selector none, and the executor the full toolset.

Phases

Proposal 1 (policy-first): 0.0s to 17.7s, finished, 7 tool calls, $0.068
Proposal 2 (state-first): 0.0s to 16.7s, finished, 7 tool calls, $0.067
Proposal 3 (outcome-first): 0.0s to 15.9s, finished, 6 tool calls, $0.062
Select: 17.7s to 34.0s, finished, 0 tool calls, $0.058
Execute: 34.0s to 49.1s, finished, 8 tool calls, $0.063

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

PhaseDurationCostTurnsToolsModel
Proposal 1 (policy-first)17.7s$0.06887claude-opus-5-5
Proposal 2 (state-first)16.7s$0.06787claude-opus-5-5
Proposal 3 (outcome-first)15.9s$0.06276claude-opus-5-5
Select16.3s$0.05820claude-opus-5-5
Execute15.1s$0.06398claude-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 propose-select --tasks support-easy --models claude-opus-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
28
failed tool calls
0
distinct tools
9

Final answer

T-1041 is triaged: it's now sev3, due 2026-03-17T17:20:00Z, and assigned to E-301 Yuki Sato. Its status changed from new to open. I re-checked the plan against the live data before making any changes, and it matched.

  • Severity: sev3. The escalation matrix rates a VPN problem with team-level impact as sev3. The ticket describes about nine people on the Berlin sales floor who can't connect. The requester is a senior person in Sales, but that doesn't change the severity, because severity comes only from the matrix.
  • Deadline: 17:20Z. The ticket had no deadline. The service desk clock reads 2026-03-17T09:20:00Z, the same time the ticket was created. The sev3 response target is 480 minutes, so the deadline is 09:20Z plus 8 hours. No earlier deadline had been promised to the requester, so nothing was moved earlier.
  • Owner: E-301 Yuki Sato. The network-primary rotation owns VPN tickets. Yuki Sato is on call for it at the deadline, with a shift running 08:00Z–20:00Z, and their user record confirms they're in that rotation.

I didn't escalate, because sev3 has no escalation rotation. I didn't change any other ticket.

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.