The calendar is a status view, not the whole archive
A history calendar can help a reader see which days have a visible status marker. It is a navigation and freshness surface. A calendar cell by itself is not a complete record and should not be treated as proof of a product, subtotal, discount, screenshot, or accepted event.
If a day is blank, that does not authorize backfilling it. If a day has a status label, follow the linked record and read the evidence scope before drawing a conclusion.
The archive is where retained records carry detail
A retained GROWTH10 archive entry should identify the event date, code, product context where available, displayed cart values, and the limits of the record. It is historical context once a newer accepted record becomes current, but it remains useful for understanding what was actually recorded on that earlier date.
Keep the archive entry and the current record distinct. A newer record does not erase earlier history, and an older archive entry should not be presented as today’s result.
How to read a history page in four steps
First, identify whether you are looking at the current record, a calendar, or an individual archive entry. Second, open the linked record rather than relying on the card label alone. Third, compare the observed date with the publication or retrieval date. Fourth, read the scope statement for what was not tested.
This approach is especially important when search results, cached pages, and the live site show different dates. The date on a search result describes retrieval or indexing context; it is not automatically the date of the accepted cart event.
Keep the record trail clear
This guide is informational. It does not provide medical advice, product-quality conclusions, purchasing instructions, or a guarantee that a future cart will produce the same result. For a current code question, use the site-specific current record and then read the stated scope.