ScaffoldBench

RunSonnet 5.5repeat 2

Gated-execute on Triage the weekend's queue on Monday morning

claude-sonnet-5-5__gated-execute__support-monday-triage__r2

Score

0.854

wrong answer
design ran as designed
Cost
$1.06
Latency
5m 52s
setup 0.0s, grading 0.0s
Turns
305
Tool calls
237
Subagents
33
Tokens in / out
958k / 31k
759,271 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 5m 52s, finished, 73 tool calls, $0.202
Review 1: close_ticket: 30.7s to 36.9s, finished, 1 tool call, $0.027
Review 2: close_ticket: 36.9s to 42.0s, finished, 1 tool call, $0.011
Review 3: merge_tickets: 42.0s to 1m 1s, finished, 8 tool calls, $0.045
Review 4: merge_tickets: 1m 1s to 1m 11s, finished, 7 tool calls, $0.027
Review 5: set_severity: 1m 11s to 1m 19s, finished, 5 tool calls, $0.021
Review 6: set_severity: 1m 19s to 1m 28s, finished, 5 tool calls, $0.022
Review 7: set_severity: 1m 28s to 1m 36s, finished, 5 tool calls, $0.021
Review 8: set_severity: 1m 36s to 1m 46s, finished, 5 tool calls, $0.022
Review 9: set_severity: 1m 46s to 1m 54s, finished, 5 tool calls, $0.023
Review 10: set_severity: 1m 54s to 2m 2s, finished, 3 tool calls, $0.019
Review 11: set_severity: 2m 2s to 2m 9s, finished, 4 tool calls, $0.021
Review 12: set_severity: 2m 9s to 2m 16s, finished, 4 tool calls, $0.021
Review 13: set_severity: 2m 16s to 2m 23s, finished, 4 tool calls, $0.022
Review 14: set_severity: 2m 23s to 2m 30s, finished, 4 tool calls, $0.022
Review 15: merge_tickets: 2m 36s to 2m 44s, finished, 4 tool calls, $0.026
Review 16: extend_sla: 2m 48s to 2m 58s, finished, 6 tool calls, $0.025
Review 17: extend_sla: 2m 58s to 3m 6s, finished, 5 tool calls, $0.024
Review 18: extend_sla: 3m 6s to 3m 13s, finished, 4 tool calls, $0.020
Review 19: extend_sla: 3m 13s to 3m 19s, finished, 3 tool calls, $0.020
Review 20: extend_sla: 3m 19s to 3m 27s, finished, 4 tool calls, $0.025
Review 21: extend_sla: 3m 27s to 3m 37s, finished, 5 tool calls, $0.028
Review 22: extend_sla: 3m 37s to 3m 45s, finished, 5 tool calls, $0.027
Review 23: extend_sla: 3m 45s to 3m 53s, finished, 4 tool calls, $0.026
Review 24: assign_ticket: 3m 53s to 4m 7s, finished, 9 tool calls, $0.036
Review 25: assign_ticket: 4m 7s to 4m 19s, finished, 7 tool calls, $0.034
Review 26: assign_ticket: 4m 19s to 4m 35s, finished, 6 tool calls, $0.030
Review 27: assign_ticket: 4m 35s to 4m 43s, finished, 5 tool calls, $0.029
Review 28: assign_ticket: 4m 43s to 4m 52s, finished, 7 tool calls, $0.031
Review 29: assign_ticket: 4m 52s to 5m 1s, finished, 6 tool calls, $0.029
Review 30: assign_ticket: 5m 1s to 5m 11s, finished, 5 tool calls, $0.031
Review 31: assign_ticket: 5m 12s to 5m 22s, finished, 5 tool calls, $0.029
Review 32: assign_ticket: 5m 22s to 5m 33s, finished, 7 tool calls, $0.033
Review 33: assign_ticket: 5m 33s to 5m 45s, finished, 7 tool calls, $0.035

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

PhaseDurationCostTurnsToolsModel
Execute5m 52s$0.2027473claude-sonnet-5-5
Review 1: close_ticket6.1s$0.02731claude-sonnet-5-5
Review 2: close_ticket5.1s$0.01131claude-sonnet-5-5
Review 3: merge_tickets19.1s$0.045108claude-sonnet-5-5
Review 4: merge_tickets9.9s$0.02797claude-sonnet-5-5
Review 5: set_severity7.9s$0.02175claude-sonnet-5-5
Review 6: set_severity9.1s$0.02275claude-sonnet-5-5
Review 7: set_severity7.9s$0.02175claude-sonnet-5-5
Review 8: set_severity9.2s$0.02275claude-sonnet-5-5
Review 9: set_severity8.9s$0.02375claude-sonnet-5-5
Review 10: set_severity7.5s$0.01953claude-sonnet-5-5
Review 11: set_severity7.1s$0.02164claude-sonnet-5-5
Review 12: set_severity6.7s$0.02164claude-sonnet-5-5
Review 13: set_severity7.2s$0.02264claude-sonnet-5-5
Review 14: set_severity7.3s$0.02264claude-sonnet-5-5
Review 15: merge_tickets8.3s$0.02664claude-sonnet-5-5
Review 16: extend_sla10.3s$0.02586claude-sonnet-5-5
Review 17: extend_sla8.1s$0.02475claude-sonnet-5-5
Review 18: extend_sla6.7s$0.02064claude-sonnet-5-5
Review 19: extend_sla5.8s$0.02053claude-sonnet-5-5
Review 20: extend_sla8.2s$0.02564claude-sonnet-5-5
Review 21: extend_sla9.5s$0.02875claude-sonnet-5-5
Review 22: extend_sla8.3s$0.02775claude-sonnet-5-5
Review 23: extend_sla8.1s$0.02664claude-sonnet-5-5
Review 24: assign_ticket13.7s$0.036119claude-sonnet-5-5
Review 25: assign_ticket12.7s$0.03497claude-sonnet-5-5
Review 26: assign_ticket15.2s$0.03086claude-sonnet-5-5
Review 27: assign_ticket8.4s$0.02975claude-sonnet-5-5
Review 28: assign_ticket8.5s$0.03197claude-sonnet-5-5
Review 29: assign_ticket9.1s$0.02986claude-sonnet-5-5
Review 30: assign_ticket10.7s$0.03175claude-sonnet-5-5
Review 31: assign_ticket10.2s$0.02975claude-sonnet-5-5
Review 32: assign_ticket11.6s$0.03397claude-sonnet-5-5
Review 33: assign_ticket11.2s$0.03597claude-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 support-monday-triage --models claude-sonnet-5-5 --repeats 1

Score breakdown

  • passT-2001 graded sev3
    1.00weight 0.02

    severity=sev3

  • passT-2001 due 2026-03-23T17:00:00Z
    1.00weight 0.02

    sla_due_at=2026-03-23T17:00:00Z

  • passT-2001 assigned to E-303
    1.00weight 0.02

    assignee=E-303

  • passT-2002 graded sev4
    1.00weight 0.02

    severity=sev4

  • passT-2002 due 2026-03-26T17:00:00Z
    1.00weight 0.02

    sla_due_at=2026-03-26T17:00:00Z

  • passT-2002 assigned to E-203
    1.00weight 0.02

    assignee=E-203

  • passT-2003 graded sev2
    1.00weight 0.02

    severity=sev2

  • passT-2003 due 2026-03-23T10:30:00Z
    1.00weight 0.02

    sla_due_at=2026-03-23T10:30:00Z

  • passT-2003 assigned to E-101
    1.00weight 0.02

    assignee=E-101

  • passT-2004 graded sev2
    1.00weight 0.02

    severity=sev2

  • passT-2004 due 2026-03-23T12:10:00Z
    1.00weight 0.02

    sla_due_at=2026-03-23T12:10:00Z

  • passT-2004 assigned to E-201
    1.00weight 0.02

    assignee=E-201

  • passT-2006 graded sev2
    1.00weight 0.02

    severity=sev2

  • passT-2006 due 2026-03-23T12:10:00Z
    1.00weight 0.02

    sla_due_at=2026-03-23T12:10:00Z

  • passT-2006 assigned to E-201
    1.00weight 0.02

    assignee=E-201

  • passT-2007 graded sev2
    1.00weight 0.02

    severity=sev2

  • passT-2007 due 2026-03-23T12:10:00Z
    1.00weight 0.02

    sla_due_at=2026-03-23T12:10:00Z

  • passT-2007 assigned to E-601
    1.00weight 0.02

    assignee=E-601

  • passT-2008 graded sev4
    1.00weight 0.02

    severity=sev4

  • passT-2008 due 2026-03-26T17:00:00Z
    1.00weight 0.02

    sla_due_at=2026-03-26T17:00:00Z

  • passT-2008 assigned to E-302
    1.00weight 0.02

    assignee=E-302

  • passT-2009 graded sev4
    1.00weight 0.02

    severity=sev4

  • passT-2009 due 2026-03-26T17:00:00Z
    1.00weight 0.02

    sla_due_at=2026-03-26T17:00:00Z

  • passT-2009 assigned to E-102
    1.00weight 0.02

    assignee=E-102

  • passT-2011 graded sev2
    1.00weight 0.02

    severity=sev2

  • passT-2011 due 2026-03-23T12:10:00Z
    1.00weight 0.02

    sla_due_at=2026-03-23T12:10:00Z

  • passT-2011 assigned to E-201
    1.00weight 0.02

    assignee=E-201

  • passT-2013 graded sev2
    1.00weight 0.02

    severity=sev2

  • passT-2013 due 2026-03-23T12:10:00Z
    1.00weight 0.02

    sla_due_at=2026-03-23T12:10:00Z

  • passT-2013 assigned to E-303
    1.00weight 0.02

    assignee=E-303

  • failT-2015 graded sev1
    0.00weight 0.02

    severity=unset

  • failT-2015 due 2026-03-23T09:10:00Z
    0.00weight 0.02

    sla_due_at=not set

  • failT-2015 assigned to E-201
    0.00weight 0.02

    assignee=unassigned

  • failT-2016 graded sev4
    0.00weight 0.02

    severity=unset

  • failT-2016 due 2026-03-26T17:00:00Z
    0.00weight 0.02

    sla_due_at=not set

  • failT-2016 assigned to E-302
    0.00weight 0.02

    assignee=unassigned

  • passT-2012 merged into T-2003
    1.00weight 0.02
  • passT-1999 merged into T-2003
    1.00weight 0.02
  • passT-2005 merged into T-2004
    1.00weight 0.02
  • passT-2010 closed as not a service request
    1.00weight 0.02
  • passT-2014 closed as not a service request
    1.00weight 0.02

Penalties

No penalties were applied.

Scorer metadata

tool calls
237
failed tool calls
0
distinct tools
17

Final answer

I triaged all 14 tickets in the new queue. One thing is still open: T-2004's deadline wasn't checked against other open tickets.

Closed as non-requests:

  • T-2010 is a SyncFlow marketing email.
  • T-2014 is an out-of-office auto-reply.

Merged duplicates:

  • T-2003: it absorbed T-2012 and T-1999, which was already open, assigned to E-101 and due 10:30Z. The reviewer caught T-1999 when I first tried to merge without it. T-2003 is the earliest-created report and carries T-1999's earlier deadline of 10:30Z. It is sev2 and assigned to E-101.
  • T-2004: it absorbed T-2005 and is sev2, due 12:10Z, assigned to E-201. I merged this one before I had listed the open tickets. I didn't check it against them afterwards, and I should have.

Severity, deadline and owner for the rest:

  • Sev2 deadlines run on the clock from the 08:10Z triage, so they fall at 12:10Z.
  • Sev3 and sev4 deadlines count business hours only, from the desk opening at 09:00 on Monday. 25 March is a company holiday, so the sev4 deadlines land on Thursday.
TicketSeverityDue (UTC)Assignee
T-2001 (Berlin VPN)sev3Mon 17:00E-303
T-2002 (CRM filter)sev4Thu 26 Mar 17:00E-203
T-2006 (payslip tax code)sev2Mon 12:10E-201
T-2007 (phishing)sev2Mon 12:10E-601
T-2008 (VPN client update)sev4Thu 26 Mar 17:00E-302
T-2009 (build logs slow)sev4Thu 26 Mar 17:00E-102
T-2011 (overtime import)sev2Mon 12:10E-201
T-2013 (Lisbon VPN)sev2Mon 12:10E-303

Judgement calls:

  • T-2006: the payroll-close amendment (KB-55) makes this single-user ticket sev2 instead of the matrix's sev3.
  • T-2007: the requester typed his password into a fake VPN login page, so it is a phishing report. That makes it sev2 and owned by the security-oncall rotation, E-601 Noor Haddad.
  • Leave cover: E-301 is on leave today, so the VPN tickets due Monday (T-2001 and T-2013) went to E-303 from the backup rotation, network-secondary. E-202 is on leave Thursday, so T-2002 went to E-203 from business-apps-secondary.
  • No major incident: nothing in the queue was company-wide, so I opened no incident and sent no pages.

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.