ScaffoldBench

RunHaiku 4.5repeat 2

Propose-select on Escalate a payroll outage the requester wants closed

claude-haiku-4-5-20251001__propose-select__support-hard__r2

Score

1.000

passed
design ran as designed
Cost
$0.222
Latency
2m 17s
setup 0.0s, grading 0.0s
Turns
44
Tool calls
38
Subagents
3
Tokens in / out
127k / 24k
64,116 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 4s, finished, 9 tool calls, $0.055
Proposal 2 (state-first): 0.0s to 43.7s, finished, 8 tool calls, $0.042
Proposal 3 (outcome-first): 0.0s to 54.5s, finished, 14 tool calls, $0.055
Select: 1m 4s to 1m 53s, finished, 0 tool calls, $0.040
Execute: 1m 53s to 2m 17s, finished, 7 tool calls, $0.031

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

PhaseDurationCostTurnsToolsModel
Proposal 1 (policy-first)1m 4s$0.055109claude-haiku-4-5-20251001
Proposal 2 (state-first)43.7s$0.04298claude-haiku-4-5-20251001
Proposal 3 (outcome-first)54.5s$0.0551514claude-haiku-4-5-20251001
Select49.0s$0.04020claude-haiku-4-5-20251001
Execute24.2s$0.03187claude-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 propose-select --tasks support-hard --models claude-haiku-4-5-20251001 --repeats 1

Score breakdown

  • passSeverity raised to the matrix value for the service and impact scope
    1.00weight 0.21

    severity=sev1 (matrix says sev1)

  • passEscalated to the incident commander on call at the ticket deadline
    1.00weight 0.29

    escalated_to=E-402 (expected E-402, on call at 2026-03-17T19:40:00Z)

  • passTicket left in status escalated rather than closed
    1.00weight 0.14

    status=escalated

  • passThe committed SLA deadline survived the escalation
    1.00weight 0.14

    sla_due_at=2026-03-17T19:40:00Z

  • passA comment records that the open linked ticket blocks closure
    1.00weight 0.14
  • passEscalation matrix read before the severity was raised
    1.00weight 0.07

Penalties

No penalties were applied.

Scorer metadata

tool calls
38
failed tool calls
0
distinct tools
8

Final answer

Perfect. All changes executed successfully. Here's the summary:

Final State of T-1070

Changes Made:

  1. ✅ Severity re-graded: sev3 → sev1 (correct per escalation matrix: payroll + company-wide impact)
  2. ✅ Escalated: To E-402 Ola Berg (incident-command rotation, on-call at 19:40 deadline) — the highest level as Grace requested
  3. ✅ Comment posted: Explains the critical blocking dependency on T-1071 (replication lag, due 10:30 UTC)
  4. ✅ Deadline preserved: 19:40:00Z (policy requires committed deadline cannot be moved earlier on re-grade/escalation)

Status for Next Shift:

  • Ticket is now escalated with proper severity
  • Routed to incident-command (highest authority level)
  • Clear visibility that T-1071 fix (10:30 deadline) is the critical path to unblocking payroll batch rerun
  • E-402 Ola Berg will take ownership when the deadline falls (18:00–06:00 shift covers the 19:40 deadline)

Why T-1070 Cannot Close Today:
Domain policy prohibits closing a ticket while a linked ticket remains open. T-1071 (replication lag blocking the batch) is open with an earlier deadline (10:30 UTC, 70 minutes away) and must be fixed first. Once T-1071 is closed, T-1070 can be immediately closed.

Handoff Complete: T-1070 is properly triaged, escalated to the highest level, and positioned for incident-command pickup.

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.