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

← the fixed question set

How does a browser decide whether to send a CORS preflight request?

u08 · 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 13.2.1: When to Evaluate 0.4949
2 RFC 9110 Section 13: Conditional Requests 0.4708
3 RFC 9110 Section 13.2.2: Precedence of Preconditions 0.4702
4 RFC 9111 Section 4.3.2: Handling a Received Validation Request 0.4635
7 RFC 9111 Section 4.3.1: Sending a Validation Request 0.4415
8 RFC 9110 Section 12.1: Proactive Negotiation 0.4333
9 RFC 9110 Section 7.3.2: To a Proxy 0.4175
10 RFC 9110 Section 13.1: Preconditions 0.4170

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

0.586 ms of a 150.0 ms deadline: retrieval 0.413 ms, drafting 0.005 ms, grounding 0.012 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/u08.