ScaffoldBench

RunSonnet 5.5repeat 2

Orchestrator-workers on Redirect the order that has not shipped

claude-sonnet-5-5__orchestrator-workers__ecommerce-easy__r2

Score

1.000

passed
design ran as designed
Cost
$0.078
Latency
27.3s
setup 0.0s, grading 0.0s
Turns
14
Tool calls
9
Subagents
2
Tokens in / out
49k / 3.0k
33,870 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 8.9s, finished, 0 tool calls, $0.016
Worker 1: update-unshipped: 8.9s to 20.7s, finished, 6 tool calls, $0.025
Worker 2: verify-shipped: 8.9s to 15.7s, finished, 3 tool calls, $0.018
Synthesize: 20.7s to 27.3s, finished, 0 tool calls, $0.019

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

PhaseDurationCostTurnsToolsModel
Decompose8.9s$0.01620claude-sonnet-5-5
Worker 1: update-unshipped11.8s$0.02576claude-sonnet-5-5
Worker 2: verify-shipped6.8s$0.01843claude-sonnet-5-5
Synthesize6.6s$0.01910claude-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 orchestrator-workers --tasks ecommerce-easy --models claude-sonnet-5-5 --repeats 1

Score breakdown

  • passThe order that has not shipped carries the new address
    1.00weight 0.43

    O-1001 address: 7 Quarry Rise, Sheffield S11 8XZ, UK

  • passThe edit did not spill onto the order already in transit
    1.00weight 0.29
  • passLooked up which order was still open before editing one
    1.00weight 0.14
  • passChecked the state of the order already in transit
    1.00weight 0.14

Penalties

No penalties were applied.

Scorer metadata

tool calls
9
failed tool calls
0
distinct tools
3

Final answer

The shipped order was not affected, but I can't confirm the address change on the unshipped order because the two reports disagree.

Order in transit (O-1002): Both workers agree it is shipped, and its one line shipped on 2026-07-07. Its address is still 88 Old Mill Road, Bristol BS3 2QQ, UK. Worker 1 read it after its update and worker 2 read it independently, so this part is confirmed. The handbook requires it to stay unchanged while in transit.

Order not yet shipped (O-1001): Both workers agree it is pending, with both lines pending (L1 and L2).

  • Worker 1 says it changed the address from 12 Alder Lane, Bristol BS1 4TR, UK to 7 Quarry Rise, Sheffield S11 8XZ, UK. It says it re-read the order and saw the new address.
  • Worker 2 says O-1001 was still on 12 Alder Lane, Bristol BS1 4TR, UK when it read it.

The reports don't give timestamps. Worker 2 may have read the order before worker 1's update, but I can't establish that from the reports. Until someone re-reads O-1001, I can't say whether the update stuck.

Other notes:

  • Worker 1 says the address is stored as a single text string, so it replaced the whole string. It did not keep any separate name or phone fields.
  • Neither worker reported changing any other order, customer, product or stock.

Next step: Re-read O-1001. If it still shows 12 Alder Lane, apply the update to that order only.

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.