ScaffoldBench

RunHaiku 4.5repeat 2

Orchestrator-workers on Triage a new service desk ticket

claude-haiku-4-5-20251001__orchestrator-workers__support-easy__r2

Score

1.000

passed
design ran as designed
Cost
$0.046
Latency
49.2s
setup 0.0s, grading 0.0s
Turns
11
Tool calls
7
Subagents
1
Tokens in / out
31k / 4.4k
14,211 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 task was decomposed: heldorchestrator-workers.decompositionThe orchestrator’s reply was read through its schema and held at least one subtask.
  • The fan-out happened: heldorchestrator-workers.fan-outEvery subtask got a worker, every worker ran, and the recorded subagent count matches.
  • The synthesis wrote the answer: heldorchestrator-workers.synthesisThe final answer came from the synthesis call, not from a worker’s report standing in for it.
  • Each call was shown the right tools: heldorchestrator-workers.toolsThe orchestrator and the synthesis were shown no tools and every worker the task’s full toolset.

Phases

Decompose: 0.0s to 15.2s, finished, 0 tool calls, $0.0099
Worker 1: all: 15.2s to 35.5s, finished, 7 tool calls, $0.026
Synthesize: 35.5s to 49.2s, finished, 0 tool calls, $0.0097

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

PhaseDurationCostTurnsToolsModel
Decompose15.2s$0.009920claude-haiku-4-5-20251001
Worker 1: all20.3s$0.02687claude-haiku-4-5-20251001
Synthesize13.7s$0.009710claude-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 orchestrator-workers --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 Completion Summary

Based on the worker report, ticket T-1041 has been successfully triaged.

The worker completed all four required actions:

  1. Severity assigned: sev3 (team-level impact VPN incident)
  2. Deadline set: 480 minutes from ticket creation (matching the response target for severity 3)
  3. Assigned to: E-301 Yuki Sato (network-primary on-call engineer for the owning rotation)
  4. Status changed: new → open

The worker inspected the ticket details before acting (identifying it as a VPN service issue affecting 9 people in the Berlin sales team), consulted the escalation matrix to determine the correct severity, calculated the SLA deadline per domain policy, and routed it to the appropriate engineer based on who is on call at the deadline time.

The task is complete.

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.