Accepted
A retained cart-only observation shows VIP10 visibly applied, with product context, cart subtotal, observed discount, and a retained screenshot. This establishes only the displayed cart response.
VIP10 Verification Protocol v1.0
Names for the records the desk actually keeps.
This protocol defines the public labels used for cart-only VIP10 observations. It does not describe an order, payment approval, fulfillment, universal eligibility, or medical use.
Manual review required
A public cart observation exists after an attempted VIP10 application, but the accepted-result evidence threshold is incomplete. It is not an accepted result or a rejection claim.
Stock unavailable
No discovered public listing was visibly eligible for the controlled guest-cart check. This is an availability record, not a conclusion about VIP10.
Checkout blocked
The public storefront did not expose enough cart-eligible context to complete the controlled observation. It is not a code outcome.
Automated primary run
A record received through the dedicated signed Cloud Computer worker. The worker discovers visible cart-eligible listings and uses deterministic date-based rotation; it records inventory skips separately.
Automated system follow-up — retired historical label
A historical origin label from the former scheduled system-follow-up method. It remains visible on retained older records but is not part of the current future-facing verification sequence.
User manual observation
A cart-only observation personally performed or supplied by the user and retained under the same public evidence rules.
User manual observation — automated-system-prepared evidence record
A user-performed cart observation whose public-safe evidence derivative and retained record were prepared by the automated system. The cart action remains identified as user manual.
User manual follow-up
A manual verification performed only when the automated primary run does not retain an accepted verification record. At most one follow-up is retained for that Vancouver evidence day, under its own manual evidence record, and it is never presented as an automated result.
Retired secondary backup verification
A historical record label for the former separately timed automated backup. It remains visible on retained historic records, but it is not part of the current future-facing verification method.
Operational context
Setup, troubleshooting, and worker status statements remain outside the verification-event taxonomy. They do not create a VIP10 accepted, rejected, or failed-code record.