ScaffoldBench

RunOpus 5.5repeat 1

Propose-select on Share two short deliveries out among backorders

claude-opus-5-5__propose-select__ecommerce-backorder-allocation__r1

Score

1.000

passed
design ran as designed
Cost
$1.46
Latency
3m 34s
setup 0.0s, grading 0.0s
Turns
207
Tool calls
201
Subagents
3
Tokens in / out
788k / 32k
690,034 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.
  • All three proposers ran: heldpropose-select.proposalsThree proposers ran in parallel, each from its own angle, and none was starved while another ran.
  • The selector chose: heldpropose-select.selectionThe selector picked a proposal by a valid number, read from its schema reply and not a default.
  • Each call was shown the right tools: heldpropose-select.toolsEach proposer was shown the read-only tools, the selector none, and the executor the full toolset.

Phases

Proposal 1 (policy-first): 0.0s to 1m 2s, finished, 43 tool calls, $0.283
Proposal 2 (state-first): 0.0s to 55.9s, finished, 42 tool calls, $0.278
Proposal 3 (outcome-first): 0.0s to 57.1s, finished, 43 tool calls, $0.280
Select: 1m 2s to 1m 27s, finished, 0 tool calls, $0.133
Execute: 1m 27s to 3m 34s, finished, 73 tool calls, $0.485

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

PhaseDurationCostTurnsToolsModel
Proposal 1 (policy-first)1m 2s$0.2834443claude-opus-5-5
Proposal 2 (state-first)55.9s$0.2784342claude-opus-5-5
Proposal 3 (outcome-first)57.1s$0.2804443claude-opus-5-5
Select25.5s$0.13320claude-opus-5-5
Execute2m 7s$0.4857473claude-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 propose-select --tasks ecommerce-backorder-allocation --models claude-opus-5-5 --repeats 1

Score breakdown

  • passO-5201 allocated from the delivery
    1.00weight 0.05

    L1=pending

  • passO-5201: customer told once that the order is allocated
    1.00weight 0.01
  • passO-5202 allocated from the delivery
    1.00weight 0.05

    L1=pending L2=pending

  • passO-5202: customer told once that the order is allocated
    1.00weight 0.01
  • passO-5203 allocated from the delivery
    1.00weight 0.05

    L1=pending

  • passO-5203: customer told once that the order is allocated
    1.00weight 0.01
  • passO-5204 allocated from the delivery
    1.00weight 0.05

    L1=pending

  • passO-5204: customer told once that the order is allocated
    1.00weight 0.01
  • passO-5206 left waiting, with a promise date
    1.00weight 0.05

    L1=backordered@2026-08-14 L2=backordered@2026-08-14 L3=pending

  • passO-5206 waiting lines promised for the date the in-transit supply gives them
    1.00weight 0.03

    expected L1@2026-08-14, L2@2026-08-14

  • passO-5206: customer told once, with the promised date
    1.00weight 0.01
  • passO-5207 allocated from the delivery
    1.00weight 0.05

    L1=pending L2=pending

  • passO-5207: customer told once that the order is allocated
    1.00weight 0.01
  • passO-5208 allocated from the delivery
    1.00weight 0.05

    L1=pending

  • passO-5208: customer told once that the order is allocated
    1.00weight 0.01
  • passO-5209 allocated from the delivery
    1.00weight 0.05

    L1=pending

  • passO-5209: customer told once that the order is allocated
    1.00weight 0.01
  • passO-5210 allocated from the delivery
    1.00weight 0.05

    L1=pending L2=pending

  • passO-5210: customer told once that the order is allocated
    1.00weight 0.01
  • passO-5211 allocated from the delivery
    1.00weight 0.05

    L1=pending L2=shipped

  • passO-5211: customer told once that the order is allocated
    1.00weight 0.01
  • passO-5212 allocated from the delivery
    1.00weight 0.05

    L1=pending

  • passO-5212: customer told once that the order is allocated
    1.00weight 0.01
  • passO-5213 left waiting, with a promise date
    1.00weight 0.05

    L1=backordered@2026-08-14

  • passO-5213 waiting lines promised for the date the in-transit supply gives them
    1.00weight 0.03

    expected L1@2026-08-14

  • passO-5213: customer told once, with the promised date
    1.00weight 0.01
  • passO-5214 left waiting, with a promise date
    1.00weight 0.05

    L1=backordered@2026-08-19

  • passO-5214 waiting lines promised for the date the in-transit supply gives them
    1.00weight 0.03

    expected L1@2026-08-19

  • passO-5214: customer told once, with the promised date
    1.00weight 0.01
  • passO-5215 allocated from the delivery
    1.00weight 0.05

    L1=pending

  • passO-5215: customer told once that the order is allocated
    1.00weight 0.01
  • passBoth deliveries were allocated in full
    1.00weight 0.03

    P-DOC stock=0, P-MON stock=0

Penalties

No penalties were applied.

Scorer metadata

tool calls
201
failed tool calls
0
distinct tools
11

Final answer

I worked the dock and monitor backorders. Twelve orders now have their stock, two are waiting with promise dates, and O-5205 was left alone because it's on risk hold. The result differs from the plan because two more purchase orders arrived while I was working. PO-91 brought 4 more laptop docks and PO-93 brought 3 more monitors. The plan had treated both as still on the way. The backorder rules cover any stock received from a supplier, so I gave the extra units out the same way and redid the promise dates.

Priority I used: I confirmed the store date (2026-07-25), the policy updates, each order's flags and the customers' tiers before acting. Update PU-12 applies, so orders placed on or before 07-11 went first, oldest first, whatever the tier. After that it was platinum, then gold, then standard, earliest order first. PU-9 only covered June, so it doesn't apply.

Stock allocated (now ready to ship):

  • Laptop docks (11 units: 7 from PO-88, 4 from PO-91):

    • O-5201 (2), O-5202 L2, O-5204 (2) as older orders.
    • O-5207 L1, allocated together with its monitor line because the order must ship complete.
    • O-5209 (2), O-5210, O-5211 L1.
    • O-5215: O-5213 needs 2 and only 1 dock was left, so the next line that fit took it.

  • Monitors (7 units: 4 from PO-89, 3 from PO-93):

    • O-5202 L1 and O-5203 (2) as older orders.
    • O-5207 L2, together with its dock.
    • O-5208 (2) and O-5212.

Promise dates for lines still waiting:

  • O-5206 L1 (dock) and L2 (USB-C hub): 2026-08-14. The dock would come from PO-95 (due 08-14) and the hub from PO-90 (due 08-06). The order must ship complete, so both lines get the later date. Dating the hub line goes slightly beyond docks and monitors. I did it because the ship-complete rule gives every waiting line on the order the latest date.
  • O-5213 L1: 2026-08-14 (PO-95).
  • O-5214 L1: 2026-08-19 (PO-97).

Customer notices: I sent 14, one per order: 11 say the stock is allocated and 3 (O-5206, O-5213, O-5214) give the expected date. O-5205 got no stock, no date and no message.

Left alone: O-5206 L3, O-5210 L2, O-5211 L2 (already shipped) and every other order and product. There were no open inbox messages.

Something to check: the reply after O-5204's allocation showed dock stock at 6 when it should have been 2. I checked the stock records, which is how I found that PO-91 had arrived. From then on I allocated one order at a time and checked purchase orders and stock again before setting dates and sending notices. Both have stayed the same since PO-93 arrived.

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.