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

← the fixed question set

What grant types does OAuth 2.0 define?

u04 · 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 11.1: Authentication Scheme 0.3751
2 RFC 9110 Section 19.2: Informative References 0.3648
3 RFC 9110 Section 9.1: Overview 0.3639
4 RFC 9110 Section 16.4.2: Considerations for New Authentication Schemes 0.3533
7 RFC 9110 Section 18.10: Upgrade Token Registration 0.3482
8 RFC 9110 Section 16: Extending HTTP 0.3458
9 RFC 9112 Section 3.1: Method 0.3444

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

0.583 ms of a 150.0 ms deadline: retrieval 0.419 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/u04.