RunHaiku 4.5repeat 1
Plan-execute on Twelve HTTP status codes, by the book
claude-haiku-4-5-20251001__plan-execute__research-status-codes__r1
Score
1.000
passed
design ran as designed- Cost
- $0.196
- Latency
- 2m 44s
- setup 0.0s, grading 0.3s
- Turns
- 23
- Tool calls
- 20
- Subagents
- 0
- Tokens in / out
- 344k / 19k
- 302,495 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.
- The plan was a plan: heldplan-execute.planThe planner’s reply was read through its schema and held at least one step.
- Each call was shown the right tools: heldplan-execute.toolsThe planner was shown no tools and the executor the task’s full toolset.
Phases
Plan: 0.0s to 1m 4s, finished, 0 tool calls, $0.037
Execute: 1m 4s to 2m 44s, finished, 20 tool calls, $0.159
Drawn from the phase records: timing and cost per call, no tool calls or messages.
| Phase | Duration | Cost | Turns | Tools | Model |
|---|---|---|---|---|---|
| Plan | 1m 4s | $0.037 | 2 | 0 | claude-haiku-4-5-20251001 |
| Execute | 1m 40s | $0.159 | 21 | 20 | claude-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
- A gate that blocked the right moveGated-execute · Haiku 4.5
- Three proposals beat one agentPropose-select · Haiku 4.5
- A verifier that earned its keepPlan-execute-verify · Sonnet 5.5
- A revision that did not helpPlan-execute-verify · Haiku 4.5
- The control, missing a stepSingle · Haiku 4.5
Record this cell yourself: npm run bench -- run --strategies plan-execute --tasks research-status-codes --models claude-haiku-4-5-20251001 --repeats 1
Score breakdown
- passstatus code 2031.00weight 0.08
quote verified in rfc9110
- passstatus code 2061.00weight 0.08
quote verified in rfc9110
- passstatus code 3031.00weight 0.08
quote verified in rfc9110
- passstatus code 3071.00weight 0.08
quote verified in rfc9110
- passstatus code 3081.00weight 0.08
quote verified in rfc9110
- passstatus code 4051.00weight 0.08
quote verified in rfc9110
- passstatus code 4101.00weight 0.08
quote verified in rfc9110
- passstatus code 4131.00weight 0.08
quote verified in rfc9110
- passstatus code 4141.00weight 0.08
quote verified in rfc9110
- passstatus code 4211.00weight 0.08
quote verified in rfc9110
- passstatus code 4221.00weight 0.08
quote verified in rfc9110
- passstatus code 5011.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","rfc9111"]
- opened by role
- {"primary":["rfc9110"],"distractor":["rfc9111"]}
- displayed share
- {"rfc9110":0.0875,"mdn-status-308":0.1219,"rfc9111":0.2099,"mdn-status-codes":0.018,"rfc7231":0.0013}
- 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 now have all the information I need. Let me compile my findings into the required JSON format. Based on my research of RFC 9110 (HTTP Semantics), I have found:
- 203: Section 15.3.4 - Explicitly marked as heuristically cacheable
- 206: Section 15.3.7 - Explicitly marked as heuristically cacheable
- 303: Section 15.4.4 - NO explicit heuristic cacheability statement
- 307: Section 15.4.8 - NO explicit heuristic cacheability statement
- 308: Section 15.4.9 - Explicitly marked as heuristically cacheable
- 405: Section 15.5.6 - Explicitly marked as heuristically cacheable
- 410: Section 15.5.11 - Explicitly marked as heuristically cacheable
- 413: Section 15.5.14 - NO explicit heuristic cacheability statement
- 414: Section 15.5.15 - Explicitly marked as heuristically cacheable
- 421: Section 15.5.20 - NO explicit heuristic cacheability statement
- 422: Section 15.5.21 - NO explicit heuristic cacheability statement
- 501: Section 15.6.2 - Explicitly marked as heuristically cacheable
According to RFC 9111 (HTTP Caching), "heuristics can only be used on responses without explicit freshness whose status codes are defined as 'heuristically cacheable'" - meaning status codes that don't have an explicit statement about heuristic cacheability in their RFC 9110 sections are not heuristically cacheable by default.
Here is my final answer:
{"answers":[{"code":"203","reason":"Non-Authoritative Information","section":"15.3.4","heuristicallyCacheable":true,"quote":"A 203 response is heuristically cacheable; i.e., unless otherwise indicated by the method definition or explicit cache controls (see Section 4.2.2 of [CACHING]).","url":"https://www.rfc-editor.org/rfc/rfc9110.html"},{"code":"206","reason":"Partial Content","section":"15.3.7","heuristicallyCacheable":true,"quote":"A 206 response is heuristically cacheable; i.e., unless otherwise indicated by explicit cache controls (see Section 4.2.2 of [CACHING]).","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.","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.","url":"https://www.rfc-editor.org/rfc/rfc9110.html"},{"code":"308","reason":"Permanent Redirect","section":"15.4.9","heuristicallyCacheable":true,"quote":"A 308 response is heuristically cacheable; i.e., unless otherwise indicated by the method definition or explicit cache controls (see Section 4.2.2 of [CACHING]).","url":"https://www.rfc-editor.org/rfc/rfc9110.html"},{"code":"405","reason":"Method Not Allowed","section":"15.5.6","heuristicallyCacheable":true,"quote":"A 405 response is heuristically cacheable; i.e., unless otherwise indicated by the method definition or explicit cache controls (see Section 4.2.2 of [CACHING]).","url":"https://www.rfc-editor.org/rfc/rfc9110.html"},{"code":"410","reason":"Gone","section":"15.5.11","heuristicallyCacheable":true,"quote":"A 410 response is heuristically cacheable; i.e., unless otherwise indicated by the method definition or explicit cache controls (see Section 4.2.2 of [CACHING]).","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":"A 414 response is heuristically cacheable; i.e., unless otherwise indicated by the method definition or explicit cache controls (see Section 4.2.2 of [CACHING]).","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).","url":"https://www.rfc-editor.org/rfc/rfc9110.html"},{"code":"501","reason":"Not Implemented","section":"15.6.2","heuristicallyCacheable":true,"quote":"A 501 response is heuristically cacheable; i.e., unless otherwise indicated by the method definition or explicit cache controls (see Section 4.2.2 of [CACHING]).","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.