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

← the fixed question set

Which HTTP request methods are defined as safe?

q04 · grounded · HTTP 200 · index 0fc1763d6701

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

The GET, HEAD, OPTIONS, and TRACE methods are defined to be safe.
rfc9110#9.2.1 — 100% of this claim's content words appear in that passage.

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

ranksectionscore
1 RFC 9110 Section 9.2.1: Safe Methods 0.7779
4 RFC 9110 Section 9.2.2: Idempotent Methods 0.5593
5 RFC 9110 Section 18.2: Method Registration 0.5515
6 RFC 9110 Section 16.1.1: Method Registry 0.5494
7 RFC 9110 Section 9.1: Overview 0.5270
8 RFC 9110 Section 16.1.2: Considerations for New Methods 0.5265
9 RFC 9110 Section 4.2: HTTP-Related URI Schemes 0.5154

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

11.52 ms of a 150.0 ms deadline: retrieval 0.419 ms, drafting 0.008 ms, grounding 0.477 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/q04.