ScaffoldBench

RunHaiku 4.5repeat 1

Single on Triage a new service desk ticket

claude-haiku-4-5-20251001__single__support-easy__r1

Score

1.000

passed
design ran as designed
Cost
$0.027
Latency
19.8s
setup 0.0s, grading 0.0s
Turns
8
Tool calls
7
Subagents
0
Tokens in / out
25k / 1.8k
14,219 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.8s, finished, 7 tool calls, $0.027

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

PhaseDurationCostTurnsToolsModel
Main19.8s$0.02787claude-haiku-4-5-20251001

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-easy --models claude-haiku-4-5-20251001 --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
7
failed tool calls
0
distinct tools
7

Final answer

Task Complete

I have successfully triaged ticket T-1041. Here's what I did:

Analysis:

  • Service: VPN (gateway connectivity issue)
  • Impact Scope: Team (9 people in Berlin sales affected)
  • Escalation Matrix Lookup: For VPN + team impact → sev3 with 480-minute response target

Actions Taken:

  1. Severity: Set to sev3 (from the escalation matrix for VPN service with team impact scope)
  2. SLA Deadline: Set to 2026-03-17T17:20:00Z (480 minutes from the triage time at 09:20:00Z)
  3. Assignment: Assigned to E-301 Yuki Sato (on call for network-primary rotation at the deadline time)
  4. Status: Automatically changed from "new" to "open" upon assignment

The ticket is now properly triaged and in the hands of the appropriate on-call engineer for the VPN service.

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.