Evidence system status
Retained records, not a promise of a future outcome.
This page separates the VIP10 code record, the method behind the latest confirmed result, primary-worker health, and the latest automated attempt. A technical interruption is never presented as a code rejection or accepted checkout result.
The current protected observation method uses one automated primary run. It remains in commissioning until it reaches 14 consecutive unattended conclusive runs and a production-ready declaration is recorded. When the primary does not retain an accepted result, at most one user manual follow-up may be retained with its own screenshot-backed cart record. The former automated system follow-up is retired and appears only as historical provenance on older retained records. Every accepted record keeps its actual origin visible and no follow-up becomes an unattended primary run.
Verification cadence
A status changes only when its dated record changes.
The protected process schedules one automated primary observation per Vancouver day. A current VIP10 result is published only when a later accepted cart record retains its own observed time, code response, item context, subtotal, discount, and evidence. A calendar change, page edit, copy action, or technical heartbeat does not create a new verification date.
Historical records remain available with their original dates. If a scheduled primary is incomplete or does not retain accepted evidence, it remains operational context and the latest accepted record keeps its actual date rather than being replaced by a generic freshness claim.
Outcome coverage
Machine-readable record
Response integrity summary
The feed digest is a SHA-256 checksum of the public record fields in the current response order. It helps a reader detect a changed response; it is not an independent timestamp, a blockchain record, or a substitute for the linked screenshot and event row.
- Algorithm
- SHA-256
- Current digest
72e17fe0f2913e41fc3840c464f25d3f28a5821e9bfd6e486112760b1daa38ac