One Verification Event, Multiple Public Surfaces: Keeping VIP10 Evidence Consistent

The event should come first

A successful VIP10 guest-cart observation has its own identity: a particular time, code, cart context, result, and event key. Public pages can then present different views of that same underlying observation.

Manually recreating the event separately on every page creates unnecessary opportunities for inconsistency.

Current status and history have different jobs

The current page answers what the latest successful documented observation is. The archive answers what successful observations were documented previously. When a new event becomes current, the previous record can move into historical context without being rewritten or erased.

Methodology explains; it does not invent another event

A methodology page explains how verification works and may reference the latest record for context, but it should not become a competing independently maintained source of current status. The verification record owns the event.

Supporting research remains downstream

A downstream resource should summarize the owning source’s published event without inventing a newer event, altering the original timestamp, or silently replacing the owning observation with its own.

Why synchronization matters

If one surface shows September 21 while another shows September 20, the discrepancy may be a stale page, cache, external retrieval delay, or genuinely separate maintenance. A shared event model makes the difference easier to diagnose because the code, timestamp, figures, and method can be compared directly.

Avoid duplicate freshness

If the accepted cart event has succeeded and been published, a downstream cache failure does not create a need for another cart observation. Publication or retrieval has failed; the evidence itself has not.