ScaffoldBench

RunSonnet 5.5repeat 1

Plan-execute-verify on Where ten HTTP header fields are defined

claude-sonnet-5-5__plan-execute-verify__research-header-fields__r1

Score

1.000

passed
design ran as designed
Cost
$0.359
Latency
1m 28s
setup 0.0s, grading 0.1s
Turns
47
Tool calls
39
Subagents
0
Tokens in / out
180k / 11k
114,889 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-verify.planThe planner’s reply was read through its schema and held at least one step.
  • Every verdict was read: heldplan-execute-verify.verdictsEvery review round ended with a verdict read from the schema reply, not a default.
  • The loop did what its verdicts said: heldplan-execute-verify.loopEvery verdict that called for a revision got one, and nothing was revised without such a verdict.
  • Each call was shown the right tools: heldplan-execute-verify.toolsThe planner was shown no tools, the verifier the read-only ones, and the executor and reviser the full toolset.

Phases

Plan: 0.0s to 10.7s, finished, 0 tool calls, $0.018
Execute: 10.7s to 43.3s, finished, 20 tool calls, $0.173
Verify: 43.3s to 59.3s, finished, 4 tool calls, $0.042
Revise (round 1): 59.3s to 1m 13s, finished, 4 tool calls, $0.068
Verify revision 1: 1m 13s to 1m 28s, finished, 11 tool calls, $0.058

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

PhaseDurationCostTurnsToolsModel
Plan10.7s$0.01820claude-sonnet-5-5
Execute32.6s$0.1732120claude-sonnet-5-5
Verify16.0s$0.04264claude-sonnet-5-5
Revise (round 1)14.0s$0.06854claude-sonnet-5-5
Verify revision 114.6s$0.0581311claude-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 plan-execute-verify --tasks research-header-fields --models claude-sonnet-5-5 --repeats 1

Score breakdown

  • passheader field Age
    1.00weight 0.10

    quote verified in rfc9111

  • passheader field Cache-Control
    1.00weight 0.10

    quote verified in rfc9111

  • passheader field Expires
    1.00weight 0.10

    quote verified in rfc9111

  • passheader field Last-Modified
    1.00weight 0.10

    quote verified in rfc9110

  • passheader field ETag
    1.00weight 0.10

    quote verified in rfc9110

  • passheader field Location
    1.00weight 0.10

    quote verified in rfc9110

  • passheader field Retry-After
    1.00weight 0.10

    quote verified in rfc9110

  • passheader field Vary
    1.00weight 0.10

    quote verified in rfc9110

  • passheader field Strict-Transport-Security
    1.00weight 0.10

    quote verified in rfc6797

  • passheader field Link
    1.00weight 0.10

    quote verified in rfc8288

Penalties

No penalties were applied.

Scorer metadata

corpus
{"version":2,"snapshot":"2026-10-01","hash":"86bd1bd14f66db67ec5c7686f5e47663ee99f16c49edb5b9384b8668854857dc","documents":9}
opened documents
["rfc9111","rfc9110","rfc6797","rfc8288"]
opened by role
{"primary":["rfc9111","rfc9110","rfc6797","rfc8288"]}
displayed share
{"rfc9111":0.2203,"rfc9110":0.0539,"rfc6797":0.108,"rfc8288":0.1825}
cited count
4
verified count
4
hallucinated count
0
citation integrity
1
hallucinated urls
[]
answer block
true
answer block repaired
false
items answered
10
item count
10
field accuracy
1
grounded items
10
field misses
{}

Final answer

Both issues were valid, and I've fixed both. I re-opened the pages in this session to check the new quotes.

  • Last-Modified: the old quote, "An example of its use is", was a fragment. It also appears in another section of RFC 9110. I replaced it with the defining sentence from section 8.8.2.
  • Strict-Transport-Security: the old quote was a generic lead-in. I replaced it with the sentence that opens section 6.1 of RFC 6797 and defines the header field.

I left the other eight entries unchanged. Sources:

{"answers":[
{"field":"Age","rfc":"9111","section":"5.1","quote":"The Age field value is a non-negative integer, representing time in seconds (see Section 1.2.2).","url":"https://www.rfc-editor.org/rfc/rfc9111.html"},
{"field":"Cache-Control","rfc":"9111","section":"5.2","quote":"Cache directives are unidirectional, in that the presence of a directive in a request does not imply that the same directive is present or copied in the response.","url":"https://www.rfc-editor.org/rfc/rfc9111.html"},
{"field":"Expires","rfc":"9111","section":"5.3","quote":"The presence of an Expires header field does not imply that the original resource will change or cease to exist at, before, or after that time.","url":"https://www.rfc-editor.org/rfc/rfc9111.html"},
{"field":"Last-Modified","rfc":"9110","section":"8.8.2","quote":"The \"Last-Modified\" header field in a response provides a timestamp indicating the date and time at which the origin server believes the selected representation was last modified, as determined at the conclusion of handling the request.","url":"https://www.rfc-editor.org/rfc/rfc9110.html"},
{"field":"ETag","rfc":"9110","section":"8.8.3","quote":"An entity tag consists of an opaque quoted string, possibly prefixed by a weakness indicator.","url":"https://www.rfc-editor.org/rfc/rfc9110.html"},
{"field":"Location","rfc":"9110","section":"10.2.2","quote":"The field value consists of a single URI-reference.","url":"https://www.rfc-editor.org/rfc/rfc9110.html"},
{"field":"Retry-After","rfc":"9110","section":"10.2.3","quote":"The Retry-After field value can be either an HTTP-date or a number of seconds to delay after receiving the response.","url":"https://www.rfc-editor.org/rfc/rfc9110.html"},
{"field":"Vary","rfc":"9110","section":"12.5.5","quote":"A proxy MUST NOT generate \"*\" in a Vary field value.","url":"https://www.rfc-editor.org/rfc/rfc9110.html"},
{"field":"Strict-Transport-Security","rfc":"6797","section":"6.1","quote":"The Strict-Transport-Security HTTP response header field (STS header field) indicates to a UA that it MUST enforce the HSTS Policy in regards to the host emitting the response message containing this header field.","url":"https://www.rfc-editor.org/rfc/rfc6797.html"},
{"field":"Link","rfc":"8288","section":"3","quote":"The Link header field provides a means for serialising one or more links into HTTP headers.","url":"https://www.rfc-editor.org/rfc/rfc8288.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.