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

← the fixed question set

What is the message sequence of the TLS 1.3 handshake?

u07 · 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 9112 Section 9.7: TLS Connection Initiation 0.5129
2 RFC 9110 Section 1.2: History and Evolution 0.5083
3 RFC 9112 Section 2: Message 0.4500
4 RFC 9112 Section 9.8: TLS Connection Closure 0.4384
5 RFC 9112 Section 11.3: Message Integrity 0.4375
7 RFC 9110 Section 6: Message Abstraction 0.4222
9 RFC 9112 Section 12.4: ALPN Protocol ID Registration 0.4197
10 RFC 9112 Section 13.1: Normative References 0.4161

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

0.657 ms of a 150.0 ms deadline: retrieval 0.461 ms, drafting 0.006 ms, grounding 0.013 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/u07.