Reading library
Explain field-level AND with counterexamples
Use two synthetic quantization examples to explain AND within title or text, distinguish it from phrase search and avoid unsupported field-weight or OR controls.
Draw field-local cases
A reader who adds memory to quantization needs to know what the extra word changes. The current q query uses multi_match with type=best_fields and operator=and over title and text. The analyzed terms must match within a matching field. It is not enough to find one term only in title and the other only in text. A match is not achieved if one keyword is in the title and the other is exclusively in the text. This explanation concerns field boundaries, not a judgment that the content answers the reader's question.
Draw a two-column worksheet labelled title and text, then list the analyzed terms the exercise assumes. Use synthetic snippets and explicitly state that both example words are assumed to remain distinct analyzed terms. Real matching depends on the actual analyzer; the illustration does not establish stemming, synonyms, punctuation handling or a character-for-character rule. It also does not require both fields to match simultaneously. One matching field can satisfy the condition, and neither the phrase's order nor the words' proximity is guaranteed by this AND explanation.
Test a title-only match
For the first paper example, put quantization memory in the synthetic title and leave the synthetic body unrelated to those two terms. Under the stated token assumptions, the title supplies both required terms. The body need not supply them again. This is a conceptual matching example, not a record claimed to exist in the archive and not a report of an executed test. The title could still describe conditions different from those the reader cares about. A term match only gives the reader material to inspect.
Now keep the example title but change the task. A person investigating the conditions of a memory measurement may need the hardware, model and method, none of which the two words establish. Show those requirements as a separate reading note. Do not award the title a higher quality badge or claim that title matches rank above body matches. Retrieval uses archive _doc order, not relevance, date or score order. The matching example explains eligibility; the position of a returned record does not validate its usefulness.
Test a split-field nonmatch
For the second paper example, place only quantization in the title and only memory in the text. Assume neither field contains the other analyzed term. Neither field then satisfies the two-term AND condition, despite the record containing both words somewhere. This contrasts with an imagined cross-field search that pools every word across the two columns. It does not compare two separate documents, and it should not be explained as a proximity rule. The missing condition is both terms within a matching field, not necessarily adjacent words.
Apply the counterexample carefully to an actual reading problem. An absent result does not prove that its terms were split across fields: availability, other filters, analyzer behavior and the bounded window also matter. If a reader broadens q to quantization alone, make that an explicit new request and retain the previous wording for comparison. Do not suggest an exposed OR toggle, phrase-search syntax, arbitrary field selection or field weights. Those controls are not in this API's documented filter contract. Your interface should not imply that a hidden switch can supply them.
Write a query explanation
A short label beside the form can say: all analyzed query terms must match within title or within text. Follow it with the two-column example when the user needs detail. Keep the submitted wording visible above the response, especially after a refinement. The helper text should distinguish this condition from exact-phrase matching and from semantic understanding. It should also distinguish q from filters such as subreddit, author, kind and min_score. Those restrictions narrow a request separately; min_score does not turn the result list into a relevance ranking.
When testing your own interface later, verify that adding a word starts a new page-1 sequence and that old responses remain attached to their original inputs. These are proposed application checks, not tests already performed by this article. Further successful retrievals cost one credit, including empty results. Preserve uncertainty in the message: no records returned for this request does not mean the topic was never discussed. Field-local AND is one explainable part of a historical, bounded search; it does not establish coverage, a complete conversation or a best answer.
