Statement
There are two kinds of claim, and a rendered surface must never let one impersonate the other. The record is what was observed and stamped — “last observed $1,374 as of 00:07 UTC.” A cached or pre-rendered byte may assert any observation of the record it can source. The offer is a purchasable claim — “book now, $1,374” — and a byte may assert it only if it can guarantee it at the moment of serving. Pages are offer-free by construction, not price-free: the record is fully renderable; only the live offer is withheld from the cache.
Failure mode prevented
A renderer bakes a purchasable claim into a cached response. By the time a user or an agent reads it, the offer has moved, expired, or never applied — the surface now advertises a transaction the system cannot honor. The reverse failure is just as bad: fear of stale offers strips the record out of the cache too, leaving a blank page over data the system already holds and could truthfully show.
Public implementation guidance
Separate the two claim types explicitly and render each on its own terms. The observed record — most recent value, its timestamp, distribution, and derived context — belongs in the first byte as stamped historical fact. The live offer is a distinct, freshness-guaranteed element that upgrades one value at serve time and is absent when it cannot be guaranteed. In structured data, express any price only as an observed statistic on a dataset, never as a purchasable offer. The offer never impersonates the record; the record never masquerades as a live offer.
Synthetic failure scenario
A cached page bakes a purchasable amount into HTML and offer schema. The transaction is no longer available when the page is served. The portable repair is to render the stamped observation as a record and reserve any purchasable claim for a bounded live element that can withhold itself.
Provenance mode: synthetic. Generalized scenario; not a production claim or certification receipt.