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

← the fixed question set

How is domain matching defined for cookies?

q18 · grounded · HTTP 200 · index 0fc1763d6701

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

A string domain-matches a given domain string if the domain string and the string are identical after canonicalization to lower case.
rfc6265#5.1.3 — 78% of this claim's content words appear in that passage.
A string domain-matches a given domain string if the domain string is a suffix of the string, the last character of the string not included in the domain string is a %x2E (.) character, and the string is a host name rather than an IP address.
rfc6265#5.1.3 — 92% of this claim's content words appear in that passage.

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

ranksectionscore
1 RFC 6265 Section 4.1.2.3: The Domain Attribute 0.6786
2 RFC 6265 Section 5.1.3: Domain Matching 0.6418
3 RFC 6265 Section 5.2.3: The Domain Attribute 0.6370
4 RFC 6265 Section 5.3: Storage Model 0.6082
6 RFC 6265 Section 5.1.4: Paths and Path-Match 0.5937
8 RFC 6265 Section 4.2.2: Semantics 0.5592
9 RFC 6265 Section 1: Introduction 0.5500
10 RFC 6265 Section 8.7: Reliance on DNS 0.5448

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

0.999 ms of a 150.0 ms deadline: retrieval 0.445 ms, drafting 0.006 ms, grounding 0.361 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/q18.