A cache hit is not a new generation

The flag says the result was stored

A cache hit on the log means this call returned a result the application already had. The text was not produced as a new generation for this call. The flag is about the source of the body, not about whether the words are correct.

A cache miss means this call did not use that store. It still does not grade the text. It only says the body was not served from the cache.

Serve time is not generation time

The timestamp on this request is when the call was served. If the log also has the time the stored text was first produced, that is a second clock. If it does not, write that the generation time was not logged.

Do not move the serve time backward or forward to invent a generation time. The hours in the text, if you need them, come from the source page, not from the cache flag.

What a cache note includes

File the request id, the cache flag, and the serve time. File a generation time only when the log has it. Quote the text as a stored result when the flag says hit.

Worked case: a hit dated as a fresh answer

Request req-840 at 2026-11-03T15:04:00Z is marked cache hit. The body says the lab closes at 8. No generation time is stored. A draft says the model wrote that sentence at 15:04.

The note says the call was served at 15:04 from cache. Generation time: not logged. The closing hour, if it matters, is checked on the hours page. 15:04 is not filed as the moment the sentence was produced.

request: req-840
served: 2026-11-03T15:04:00Z
cache: hit
generation time: not logged
body: lab closes at 8
write: served from cache
not: generated at 15:04