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

← the fixed question set

How is the signature of a JSON Web Token computed?

u05 · 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 8259 Section 2: JSON Grammar 0.3930
2 RFC 9110 Section 5.6.2: Tokens 0.3764
3 RFC 8259 Section 13: Examples 0.3651
4 RFC 9110 Section 11.2: Authentication Parameters 0.3620
5 RFC 8259 Section 10: Generators 0.3569
6 RFC 8259 Section 11: IANA Considerations 0.3493
7 RFC 8259 Section 1.2: Specifications of JSON 0.3462
8 RFC 8259 Section 14.1: Normative References 0.3441
9 RFC 8259 Section 12: Security Considerations 0.3441
10 RFC 8259 Section 14.2: Informative References 0.3399

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

0.601 ms of a 150.0 ms deadline: retrieval 0.425 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/u05.