ScaffoldBench

RunSonnet 5.5repeat 1

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

claude-sonnet-5-5__gated-execute__support-monday-triage__r1

Score

0.805

wrong answer
design ran as designed
Cost
$0.992
Latency
4m 52s
setup 0.0s, grading 0.0s
Turns
295
Tool calls
230
Subagents
32
Tokens in / out
866k / 29k
681,827 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 4m 52s, finished, 67 tool calls, $0.180
Review 1: merge_tickets: 29.4s to 38.3s, finished, 6 tool calls, $0.039
Review 2: merge_tickets: 38.3s to 52.3s, finished, 9 tool calls, $0.034
Review 3: close_ticket: 52.3s to 57.4s, finished, 1 tool call, $0.011
Review 4: close_ticket: 57.4s to 1m 2s, finished, 1 tool call, $0.012
Review 5: set_severity: 1m 2s to 1m 10s, finished, 5 tool calls, $0.020
Review 6: set_severity: 1m 10s to 1m 15s, finished, 3 tool calls, $0.016
Review 7: set_severity: 1m 15s to 1m 23s, finished, 5 tool calls, $0.020
Review 8: set_severity: 1m 23s to 1m 29s, finished, 5 tool calls, $0.021
Review 9: set_severity: 1m 29s to 1m 38s, finished, 5 tool calls, $0.023
Review 10: set_severity: 1m 38s to 1m 43s, finished, 3 tool calls, $0.017
Review 11: set_severity: 1m 43s to 1m 49s, finished, 3 tool calls, $0.017
Review 12: set_severity: 1m 49s to 1m 55s, finished, 3 tool calls, $0.018
Review 13: set_severity: 1m 55s to 2m 0s, finished, 3 tool calls, $0.017
Review 14: set_severity: 2m 0s to 2m 7s, finished, 3 tool calls, $0.019
Review 15: extend_sla: 2m 7s to 2m 18s, finished, 5 tool calls, $0.026
Review 16: extend_sla: 2m 18s to 2m 25s, finished, 5 tool calls, $0.025
Review 17: extend_sla: 2m 26s to 2m 32s, finished, 4 tool calls, $0.020
Review 18: extend_sla: 2m 32s to 2m 38s, finished, 3 tool calls, $0.020
Review 19: extend_sla: 2m 38s to 2m 46s, finished, 5 tool calls, $0.027
Review 20: extend_sla: 2m 46s to 2m 53s, finished, 5 tool calls, $0.026
Review 21: extend_sla: 2m 53s to 3m 1s, finished, 4 tool calls, $0.025
Review 22: extend_sla: 3m 1s to 3m 8s, finished, 5 tool calls, $0.027
Review 23: assign_ticket: 3m 9s to 3m 21s, finished, 7 tool calls, $0.033
Review 24: assign_ticket: 3m 21s to 3m 30s, finished, 8 tool calls, $0.036
Review 25: assign_ticket: 3m 30s to 3m 38s, finished, 5 tool calls, $0.026
Review 26: assign_ticket: 3m 38s to 3m 44s, finished, 5 tool calls, $0.025
Review 27: assign_ticket: 3m 44s to 3m 54s, finished, 7 tool calls, $0.036
Review 28: assign_ticket: 3m 54s to 4m 5s, finished, 10 tool calls, $0.041
Review 29: assign_ticket: 4m 5s to 4m 12s, finished, 7 tool calls, $0.030
Review 30: assign_ticket: 4m 12s to 4m 20s, finished, 7 tool calls, $0.032
Review 31: assign_ticket: 4m 20s to 4m 32s, finished, 8 tool calls, $0.038
Review 32: assign_ticket: 4m 32s to 4m 44s, finished, 8 tool calls, $0.036

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

PhaseDurationCostTurnsToolsModel
Execute4m 52s$0.1806867claude-sonnet-5-5
Review 1: merge_tickets8.9s$0.03986claude-sonnet-5-5
Review 2: merge_tickets14.0s$0.034119claude-sonnet-5-5
Review 3: close_ticket5.1s$0.01131claude-sonnet-5-5
Review 4: close_ticket4.8s$0.01231claude-sonnet-5-5
Review 5: set_severity7.6s$0.02075claude-sonnet-5-5
Review 6: set_severity5.6s$0.01653claude-sonnet-5-5
Review 7: set_severity7.1s$0.02075claude-sonnet-5-5
Review 8: set_severity6.8s$0.02175claude-sonnet-5-5
Review 9: set_severity8.2s$0.02375claude-sonnet-5-5
Review 10: set_severity5.8s$0.01753claude-sonnet-5-5
Review 11: set_severity5.7s$0.01753claude-sonnet-5-5
Review 12: set_severity6.0s$0.01853claude-sonnet-5-5
Review 13: set_severity5.5s$0.01753claude-sonnet-5-5
Review 14: set_severity6.9s$0.01953claude-sonnet-5-5
Review 15: extend_sla10.2s$0.02675claude-sonnet-5-5
Review 16: extend_sla7.8s$0.02575claude-sonnet-5-5
Review 17: extend_sla6.1s$0.02064claude-sonnet-5-5
Review 18: extend_sla6.5s$0.02053claude-sonnet-5-5
Review 19: extend_sla8.1s$0.02775claude-sonnet-5-5
Review 20: extend_sla7.2s$0.02675claude-sonnet-5-5
Review 21: extend_sla7.4s$0.02564claude-sonnet-5-5
Review 22: extend_sla7.1s$0.02775claude-sonnet-5-5
Review 23: assign_ticket11.3s$0.03397claude-sonnet-5-5
Review 24: assign_ticket9.6s$0.036108claude-sonnet-5-5
Review 25: assign_ticket7.2s$0.02675claude-sonnet-5-5
Review 26: assign_ticket6.0s$0.02575claude-sonnet-5-5
Review 27: assign_ticket10.5s$0.03697claude-sonnet-5-5
Review 28: assign_ticket10.6s$0.0411210claude-sonnet-5-5
Review 29: assign_ticket7.8s$0.03097claude-sonnet-5-5
Review 30: assign_ticket7.6s$0.03297claude-sonnet-5-5
Review 31: assign_ticket11.8s$0.038108claude-sonnet-5-5
Review 32: assign_ticket12.3s$0.036108claude-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

  • failT-2003 due 2026-03-23T10:30:00Z
    0.00weight 0.02

    sla_due_at=2026-03-23T12:10: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
  • failT-1999 merged into T-2003
    0.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
230
failed tool calls
3
distinct tools
16

Final answer

All 14 tickets from the weekend queue are triaged: 10 are now open and assigned, 2 duplicates are merged into their survivors, and 2 non-requests are closed. I didn't escalate or page anyone, and no ticket needed a major incident.

Closed as not service requests

  • T-2010: external SyncFlow marketing email.
  • T-2014: automatic out-of-office reply.

Merged

  • T-2012 went into T-2003, the earlier report of the Payments build failures.
  • T-2005 went into T-2004, the earlier report of the CRM search errors.
  • Each survivor took the broadest impact (department) and a 12:10 deadline. Neither ticket in either pair had a prior deadline.
  • I left Berlin VPN (T-2001) and Lisbon VPN (T-2013) separate. They are different offices, and nothing shows they are the same problem.

Severity, deadline and owner for the other tickets

TicketSevDue (UTC)Assignee
T-2013 Lisbon VPNsev203-23 12:10E-303
T-2001 Berlin VPNsev303-23 17:00E-303
T-2008 VPN client updatesev403-26 17:00E-302
T-2007 phishing reportsev203-23 12:10E-601 (security-oncall)
T-2002 CRM filtersev403-26 17:00E-203
T-2004 CRM search (merged)sev203-23 12:10E-201
T-2006 payslip tax codesev203-23 12:10E-201
T-2011 overtime importsev203-23 12:10E-201
T-2003 payments builds (merged)sev203-23 12:10E-101
T-2009 build logs slowsev403-26 17:00E-102
  • Phishing: T-2007 came in on VPN, but the requester typed his password into a fake page. The handbook makes that a sev2 security incident owned by security-oncall.
  • Payroll amendment: T-2006 is single-user payroll, which the matrix rates sev3. KB-55 overrides that to sev2 until 03-31, so I used sev2.
  • Deadlines: Sev2 deadlines are 240 minutes from the 08:10 triage, on the clock. Sev3 and sev4 deadlines count business hours only, starting when the desk opens at 09:00. The sev3 deadline lands at 17:00 today. The sev4 deadlines skip the 25 March company holiday, so they land at 17:00 on Thursday.
  • Leave cover: E-301 (network-primary) is on leave today and E-202 (business-apps) is on leave on 26 March. The backup rotations cover instead. network-secondary's on-call, E-303, took the two VPN tickets due today. business-apps-secondary's on-call, E-203, took T-2002 (due 26 March). E-302 is on call for network-primary on 26 March and took T-2008.

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.