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

← the fixed question set

How is the end of a chunked message body signalled?

q15 · grounded · HTTP 200 · index 0fc1763d6701

What survived the check — each claim with the passage that supports it

RFC 9112 Section 7.1 states that the chunked transfer coding is complete when a chunk with a chunk-size of zero is received, possibly followed by a trailer section, and finally terminated by an empty line.
rfc9112#7.1 — 94% of this claim's content words appear in that passage.
RFC 9112 Section 8 states that a message body using the chunked transfer coding is incomplete if the zero-sized chunk that terminates the encoding has not been received.
rfc9112#8 — 85% of this claim's content words appear in that passage.

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

ranksectionscore
1 RFC 9112 Section 7.1: Chunked Transfer Coding 0.6284
2 RFC 9112 Section 6.3: Message Body Length 0.5986
3 RFC 9112 Section 7.1.1: Chunk Extensions 0.5984
5 RFC 9112 Section 8: Handling Incomplete Messages 0.5519
7 RFC 9112 Section 7.1.3: Decoding Chunked 0.5343

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

1.177 ms of a 150.0 ms deadline: retrieval 0.397 ms, drafting 0.005 ms, grounding 0.63 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/q15.