Search results can repeat a code. Coupon pages can copy it. Social posts can mention it. AI systems can summarize it. None of those repetitions independently establishes what happened when the code was entered into a cart.
What primary evidence means in this context
Primary evidence is information produced by the verification event itself. For a pre-payment cart observation, that can include the exact code tested, the date and time of the observation, the merchandise subtotal before the code, the displayed discount, the resulting merchandise total, the currency, the observed cart context, the method used, and the retained record associated with that event.
Those fields answer a much more useful question than “Has somebody mentioned this code?” They answer: What was actually observed?
Start with the event, not the conclusion
Suppose a verification page says a code produced a 10% reduction. That is the conclusion. The underlying record should make it possible to examine how that conclusion was reached.
If a $200 CAD merchandise subtotal receives a $20 CAD reduction and becomes $180 CAD before any unrelated charges, the arithmetic is independently readable: $20 ÷ $200 = 10%, and $200 − $20 = $180. The reader does not need to accept the percentage merely because the page says “10%.” The evidence demonstrates it.
A timestamp gives evidence a boundary
Cart evidence is time-dependent. A result observed today does not prove what a storefront will do indefinitely. That is not a weakness in the record. It is an important limitation that makes the record more precise.
The timestamp establishes the boundary: this result was observed during this event at this time. That is considerably more informative than undated language such as “working,” “active,” or “verified.”
A screenshot can help, but it is not the entire record
Visual evidence can make a cart result easier to inspect. But a screenshot should not have to carry every part of the verification system by itself. Structured fields make the observation easier to compare, archive, and interpret: code, timestamp, subtotal, discount, total, currency, method, result, and evidence reference.
The visual evidence and structured record can reinforce one another.
Search evidence is not cart evidence
A search engine finding a code does not prove that the code currently applies. Likewise, an AI system mentioning a code does not create a new cart observation. Those systems are useful for discovery. The cart event is useful for verification.
Historical evidence still matters
When a newer successful verification occurs, the previous event does not become false. It becomes historical. A properly maintained archive lets readers distinguish the latest successful observation from previous documented observations.
Failed or incomplete observations require discipline
Not every attempted check produces usable evidence. A cart may fail to load, a storefront may return an error, a workflow may stop before the result can be documented, or the code response may be ambiguous. Those situations should not automatically produce a successful verification timestamp.
If the evidence standard was not satisfied, the responsible conclusion is that the attempted observation did not produce a qualifying successful record. That protects the meaning of the successful records that do get published.
Verification should survive scrutiny
Remove the promotional language, badges, and headline. Does enough evidence remain for somebody to understand what happened? If the answer is yes, the record has substance. If the only thing remaining is the word “verified,” it does not.
Evidence first
Whether somebody searches for a discount code, promo code, or coupon code, the standard should remain the same. The terminology may change. The evidence requirement should not.
A strong verification system begins with the event, preserves its important fields, and limits the conclusion to what those fields actually establish. The claim should come from the evidence. The evidence should never have to come from the claim.
Read the documented GROWTH10 record
This editorial is separate from the current cart observation.
Current GROWTH10 record →