Trackers describe, not predict

A complete log is useful for display audits and sample analysis. It becomes misleading when presented as timing or prediction evidence.

The missing piece

History can verify what was recorded but cannot force an independent next outcome.

A precise number or polished seal can still be incomplete. Ask who produced it, what exact entity or version it covers, what date it describes and which comparison or denominator is missing.

A three-step evidence test

1. Define the claim. Write the exact proposition without promotional adjectives.
2. Match the source. Prefer a regulator, provider rule file or complete contract for the fact in question.
3. Keep the boundary. Do not extend one screenshot, case or configuration to the whole service.

What this does not prove

Even strong evidence about one mechanic does not establish operator legality, reliability or suitability. Keep product, payment, entity and jurisdiction questions separate, then join them only where a source actually does.

Apply it to Rich Prize claims