ScaffoldBench

RunOpus 5.5repeat 1

Orchestrator-workers on Run the major-incident runbook for a CI outage

claude-opus-5-5__orchestrator-workers__support-major-incident__r1

Score

0.820

wrong answer
design ran as designed
Cost
$0.310
Latency
1m 24s
setup 0.0s, grading 0.0s
Turns
43
Tool calls
39
Subagents
1
Tokens in / out
196k / 8.1k
178,392 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 11.9s, finished, 0 tool calls, $0.028
Worker 1: all: 11.9s to 1m 6s, finished, 39 tool calls, $0.229
Synthesize: 1m 6s to 1m 24s, finished, 0 tool calls, $0.054

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

PhaseDurationCostTurnsToolsModel
Decompose11.9s$0.02820claude-opus-5-5
Worker 1: all54.1s$0.2294039claude-opus-5-5
Synthesize18.4s$0.05410claude-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 orchestrator-workers --tasks support-major-incident --models claude-opus-5-5 --repeats 1

Score breakdown

  • passAn incident is open for the build pipeline
    1.00weight 0.04
  • passThe incident-command engineer on call now commands the incident
    1.00weight 0.08

    commander=E-401 (expected E-401)

  • passThe commander was paged
    1.00weight 0.04
  • passT-3101 linked to the incident
    1.00weight 0.04
  • passT-3101 kept open, raised to sev1 with its deadline intact
    1.00weight 0.02

    status=open severity=sev1 due=2026-03-30T18:52:00Z (expected sev1, 2026-03-30T18:52:00Z)

  • passT-3102 linked to the incident
    1.00weight 0.04
  • passT-3102 kept open, raised to sev1 with its deadline intact
    1.00weight 0.02

    status=open severity=sev1 due=2026-03-30T18:58:00Z (expected sev1, 2026-03-30T18:58:00Z)

  • passT-3103 linked to the incident
    1.00weight 0.04
  • passT-3103 kept open, raised to sev1 with its deadline intact
    1.00weight 0.02

    status=open severity=sev1 due=2026-03-30T19:01:00Z (expected sev1, 2026-03-30T19:01:00Z)

  • passT-3104 linked to the incident
    1.00weight 0.04
  • passT-3104 kept open, raised to sev1 with its deadline intact
    1.00weight 0.02

    status=open severity=sev1 due=2026-03-31T15:05:00Z (expected sev1, 2026-03-31T15:05:00Z)

  • passT-3105 linked to the incident
    1.00weight 0.04
  • passT-3105 kept open, raised to sev1 with its deadline intact
    1.00weight 0.02

    status=open severity=sev1 due=2026-04-01T15:07:00Z (expected sev1, 2026-04-01T15:07:00Z)

  • passT-3106 linked to the incident
    1.00weight 0.04
  • passT-3106 kept open, raised to sev1 with its deadline intact
    1.00weight 0.02

    status=new severity=sev1 due=2026-03-30T16:20:00Z (expected sev1, 2026-03-30T16:20:00Z)

  • passT-3109 linked to the incident
    1.00weight 0.04
  • passT-3109 kept open, raised to sev1 with its deadline intact
    1.00weight 0.02

    status=new severity=sev1 due=2026-03-30T16:20:00Z (expected sev1, 2026-03-30T16:20:00Z)

  • failT-3112 linked to the incident
    0.00weight 0.04
  • failT-3112 kept open, raised to sev1 with its deadline intact
    0.00weight 0.02

    status=new severity=unset due=- (expected sev1, 2026-03-30T16:20:00Z)

  • failT-3113 linked to the incident
    0.00weight 0.04
  • failT-3113 kept open, raised to sev1 with its deadline intact
    0.00weight 0.02

    status=open severity=sev3 due=2026-03-31T15:13:00Z (expected sev1, 2026-03-31T15:13:00Z)

  • failT-3114 linked to the incident
    0.00weight 0.04
  • failT-3114 kept open, raised to sev1 with its deadline intact
    0.00weight 0.02

    status=open severity=sev3 due=2026-03-31T15:16:00Z (expected sev1, 2026-03-31T15:16:00Z)

  • passThe engineer covering comms right now is the communications lead
    1.00weight 0.08

    comms=E-803 (expected E-803)

  • passA status update in the runbook form, with the next update due within 30 minutes
    1.00weight 0.08
  • passA postmortem ticket for the service, linked to the incident, due at close of business five business days on
    1.00weight 0.08

    T-3115 due=2026-04-08T17:00:00Z

Penalties

No penalties were applied.

Scorer metadata

tool calls
39
failed tool calls
0
distinct tools
18

Final answer

Build-pipeline outage: major incident INC-1 is open and the runbook steps are done

I declared the outage a major incident and ran the current runbook, KB-40. KB-39 is the 2025 edition that KB-40 replaced, so it wasn't used. All times are UTC, and the desk clock read 2026-03-30 15:20.

What was done:

  1. Incident opened: INC-1, "Build pipeline outage: no build runners available company-wide", was opened before anyone was contacted.
  2. Incident commander: I paged E-401 Priya Raman, who is on call for incident-command until 16:00 and isn't on leave. No one else was paged.

  3. Reports linked: seven reports of jobs never getting a runner are linked to INC-1: T-3101, T-3102, T-3103, T-3104, T-3105, T-3106 and T-3109.

    • T-3107 was left out. It is a flaky payments-service test that passes on retry and was reported before the outage.
    • T-3108 was left out. It is a local build failing after an Xcode upgrade.

  4. Severity: all seven linked reports are now sev1.

    • Deadlines already set on them were not changed.
    • T-3106 and T-3109 had no deadline. Each now has one under the triage rule: 15:20 plus the 60-minute sev1 target, which is 16:20.

  5. Comms lead: E-803 Elif Demir.

    • Mia Laurent (E-801) is on the comms rota but on sick leave 30–31 March.
    • The backup rotation, comms-secondary, has Elif on call now.
  6. First status update posted: "Impact: All teams company-wide; CI builds and release pipelines cannot run because no build runners are available. Started: 14:52 UTC. Next update: 15:50 UTC." The start time is when the first report, T-3101, came in.

  7. Postmortem ticket: T-3115 is open, linked to INC-1 and due 2026-04-08 17:00.

    • That is close of business on the fifth business day after 30 March.
    • It skips the Good Friday (3 April) and Easter Monday (6 April) holidays.

Deliberately not done:

  • No merges. The runbook says to link duplicates, not merge them. If they are merged later, T-3101 would survive as the earliest report and carry the earliest deadline.
  • No reassignments or closures. T-3101 is still with E-101. Whether the linked tickets' owners match who is on call when their deadlines fall was not checked.
  • No severity on T-3115. The runbook doesn't ask for one.

Still open and time-critical:

  • 15:50: the next status update is due. It hasn't been posted or scheduled.
  • 16:00: the incident-command shift passes from Priya Raman to E-402 Ola Berg. No handover has been arranged.
  • 16:20: T-3106 and T-3109 are due. T-3101 is due at 18:52.
  • T-3109's 15:30 release is blocked by the outage.

The incident is running, but it isn't finished. Someone needs to own the 15:50 update and the 16:00 command handover now.

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.