rag-contract question answering over a fixed corpus, with a measured contract

← the fixed question set

What fields does an HTTP/2 HEADERS frame contain?

u02 · unsupported · HTTP 200 · index 0fc1763d6701
eval/questions.yaml annotates this question as unsupported, and the gate holds the service to agreeing with that annotation across the set.

This corpus does not answer that question. Nothing drafted from the passages below could be traced back to them, so no answer is given.

What was retrieved — the passages the drafter saw, and nothing else

ranksectionscore
1 RFC 9110 Section 5: Fields 0.6044
2 RFC 9110 Section 6.3: Header Fields 0.5836
3 RFC 9110 Section 9.3.2: HEAD 0.5754
4 RFC 9110 Section B.2: Changes from RFC 7230 0.5506
5 RFC 9110 Section B.3: Changes from RFC 7231 0.5385
6 RFC 9110 Section 6: Message Abstraction 0.5315
7 RFC 9110 Section 19.2: Informative References 0.5243
8 RFC 9110 Section 6.1: Framing and Completeness 0.5231
9 RFC 9110 Section 5.1: Field Names 0.5229

What this request spent — against the deadline it was held to

0.656 ms of a 150.0 ms deadline: retrieval 0.454 ms, drafting 0.005 ms, grounding 0.015 ms. A request that spends the whole of it is abandoned rather than answered — a grounding check stopped part way through has not checked the remaining claims.

The same answer as JSON: /answer/u02.