ScaffoldBench

RunSonnet 5.5repeat 1

Gated-execute on Rebook onto the earliest available flight and settle the difference

claude-sonnet-5-5__gated-execute__airline-medium__r1

Score

1.000

passed
design ran as designed
Cost
$0.100
Latency
28.1s
setup 0.0s, grading 0.0s
Turns
22
Tool calls
17
Subagents
2
Tokens in / out
62k / 2.7k
43,295 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.
  • Every state change was reviewed: heldgated-execute.reviewedEvery call that changed the world had been allowed by a review before it ran, counted from the world’s own journal.
  • Every decision was read: heldgated-execute.decisionsEvery review that ran to its end gave its decision through the schema; an unreadable one is a denial.
  • Each call was shown the right tools: heldgated-execute.toolsThe executor was shown the task’s full toolset and each reviewer the read-only tools.

Phases

Execute: 0.0s to 28.1s, finished, 7 tool calls, $0.043
Review 1: change_flight: 6.6s to 15.9s, finished, 5 tool calls, $0.034
Review 2: charge_fee: 17.4s to 25.3s, finished, 5 tool calls, $0.023

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

PhaseDurationCostTurnsToolsModel
Execute28.1s$0.04387claude-sonnet-5-5
Review 1: change_flight9.3s$0.03475claude-sonnet-5-5
Review 2: charge_fee7.9s$0.02375claude-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 gated-execute --tasks airline-medium --models claude-sonnet-5-5 --repeats 1

Score breakdown

  • passReservation moved to the earliest flight with an available seat, same cabin
    1.00weight 0.43

    booked on AA204, expected AA204

  • passExactly one fee, the fare difference for the flight actually booked
    1.00weight 0.43

    fare difference owed on the booked flight: 8000 cents

  • passExactly one economy seat moved from the old flight to the new one
    1.00weight 0.14

Penalties

No penalties were applied.

Scorer metadata

tool calls
17
failed tool calls
0
distinct tools
8

Final answer

I moved Dana Whitfield's reservation R2087 from AA210 (17:40) to AA204, which departs SFO at 09:05 on 2026-08-03. She stays in economy.

  • Why AA204: It's the earliest flight that day with an economy seat. UA88 (06:15) has no economy seats left. AA918 (07:30) is cancelled.
  • Change fee: $0. Dana is gold tier, and gold is exempt from the economy change fee of $75.
  • Fare difference: I charged $80.00 to the reservation as a fare_difference entry. AA204 economy is $390 and she paid $310. No tier is exempt from this charge.

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.