ScaffoldBench

RunHaiku 4.5repeat 1

Single on Twelve HTTP status codes, by the book

claude-haiku-4-5-20251001__single__research-status-codes__r1

Score

1.000

passed
design ran as designed
Cost
$0.107
Latency
1m 5s
setup 0.1s, grading 0.4s
Turns
15
Tool calls
14
Subagents
0
Tokens in / out
203k / 6.4k
170,959 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.
  • Each call was shown the right tools: heldsingle.toolsThe agent was shown exactly the task’s tools, none missing and none extra.

Phases

Main: 0.0s to 1m 5s, finished, 14 tool calls, $0.107

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

PhaseDurationCostTurnsToolsModel
Main1m 5s$0.1071514claude-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 single --tasks research-status-codes --models claude-haiku-4-5-20251001 --repeats 1

Score breakdown

  • passstatus code 203
    1.00weight 0.08

    quote verified in rfc9110

  • passstatus code 206
    1.00weight 0.08

    quote verified in rfc9110

  • passstatus code 303
    1.00weight 0.08

    quote verified in rfc9110

  • passstatus code 307
    1.00weight 0.08

    quote verified in rfc9110

  • passstatus code 308
    1.00weight 0.08

    quote verified in rfc9110

  • passstatus code 405
    1.00weight 0.08

    quote verified in rfc9110

  • passstatus code 410
    1.00weight 0.08

    quote verified in rfc9110

  • passstatus code 413
    1.00weight 0.08

    quote verified in rfc9110

  • passstatus code 414
    1.00weight 0.08

    quote verified in rfc9110

  • passstatus code 421
    1.00weight 0.08

    quote verified in rfc9110

  • passstatus code 422
    1.00weight 0.08

    quote verified in rfc9110

  • passstatus code 501
    1.00weight 0.08

    quote verified in rfc9110

Penalties

No penalties were applied.

Scorer metadata

corpus
{"version":2,"snapshot":"2026-10-01","hash":"9841e181cc36236e3bc98c18c73e938cf003a35611d0f06c8d8da6ee7161ee1f","documents":6}
opened documents
["rfc9110"]
opened by role
{"primary":["rfc9110"]}
displayed share
{"rfc9110":0.1192,"mdn-status-308":0.1219,"rfc7231":0.0013,"mdn-status-codes":0.0184,"rfc9111":0.0032}
cited count
1
verified count
1
hallucinated count
0
citation integrity
1
hallucinated urls
[]
answer block
true
answer block repaired
false
items answered
12
item count
12
field accuracy
1
grounded items
12
field misses
{}

Final answer

Perfect! I found the overview section that lists which status codes are heuristically cacheable. Now I have all the information I need. Let me compile the final answer with exact quotes and section numbers.

Based on my research of RFC 9110 (HTTP Semantics), here is the information for each status code:

From the RFC 9110 Overview of Status Codes (Section 15.1), it explicitly states which codes are heuristically cacheable: "200, 203, 204, 206, 300, 301, 308, 404, 405, 410, 414, and 501". All other status codes are not heuristically cacheable according to this specification.

{"answers":[{"code":"203","reason":"Non-Authoritative Information","section":"15.3.4","heuristicallyCacheable":true,"quote":"The 203 (Non-Authoritative Information) status code indicates that the request was successful but the enclosed content has been modified from that of the origin server's 200 (OK) response.","url":"https://www.rfc-editor.org/rfc/rfc9110.html"},{"code":"206","reason":"Partial Content","section":"15.3.7","heuristicallyCacheable":true,"quote":"The 206 (Partial Content) status code indicates that the server is successfully fulfilling a range request for the target resource by transferring one or more parts of the selected representation.","url":"https://www.rfc-editor.org/rfc/rfc9110.html"},{"code":"303","reason":"See Other","section":"15.4.4","heuristicallyCacheable":false,"quote":"The 303 (See Other) status code indicates that the server is redirecting the user agent to a different resource, as indicated by a URI in the Location header field, which is intended to provide an indirect response to the original request.","url":"https://www.rfc-editor.org/rfc/rfc9110.html"},{"code":"307","reason":"Temporary Redirect","section":"15.4.8","heuristicallyCacheable":false,"quote":"The 307 (Temporary Redirect) status code indicates that the target resource resides temporarily under a different URI and the user agent MUST NOT change the request method if it performs an automatic redirection to that URI.","url":"https://www.rfc-editor.org/rfc/rfc9110.html"},{"code":"308","reason":"Permanent Redirect","section":"15.4.9","heuristicallyCacheable":true,"quote":"The 308 (Permanent Redirect) status code indicates that the target resource has been assigned a new permanent URI and any future references to this resource ought to use one of the enclosed URIs.","url":"https://www.rfc-editor.org/rfc/rfc9110.html"},{"code":"405","reason":"Method Not Allowed","section":"15.5.6","heuristicallyCacheable":true,"quote":"The 405 (Method Not Allowed) status code indicates that the method received in the request-line is known by the origin server but not supported by the target resource.","url":"https://www.rfc-editor.org/rfc/rfc9110.html"},{"code":"410","reason":"Gone","section":"15.5.11","heuristicallyCacheable":true,"quote":"The 410 (Gone) status code indicates that access to the target resource is no longer available at the origin server and that this condition is likely to be permanent.","url":"https://www.rfc-editor.org/rfc/rfc9110.html"},{"code":"413","reason":"Content Too Large","section":"15.5.14","heuristicallyCacheable":false,"quote":"The 413 (Content Too Large) status code indicates that the server is refusing to process a request because the request content is larger than the server is willing or able to process.","url":"https://www.rfc-editor.org/rfc/rfc9110.html"},{"code":"414","reason":"URI Too Long","section":"15.5.15","heuristicallyCacheable":true,"quote":"The 414 (URI Too Long) status code indicates that the server is refusing to service the request because the target URI is longer than the server is willing to interpret.","url":"https://www.rfc-editor.org/rfc/rfc9110.html"},{"code":"421","reason":"Misdirected Request","section":"15.5.20","heuristicallyCacheable":false,"quote":"The 421 (Misdirected Request) status code indicates that the request was directed at a server that is unable or unwilling to produce an authoritative response for the target URI.","url":"https://www.rfc-editor.org/rfc/rfc9110.html"},{"code":"422","reason":"Unprocessable Content","section":"15.5.21","heuristicallyCacheable":false,"quote":"The 422 (Unprocessable Content) status code indicates that the server understands the content type of the request content (hence a 415 (Unsupported Media Type) status code is inappropriate), and the syntax of the request content is correct, but it was unable to process the contained instructions.","url":"https://www.rfc-editor.org/rfc/rfc9110.html"},{"code":"501","reason":"Not Implemented","section":"15.6.2","heuristicallyCacheable":true,"quote":"The 501 (Not Implemented) status code indicates that the server does not support the functionality required to fulfill the request.","url":"https://www.rfc-editor.org/rfc/rfc9110.html"}]}

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.