Signal
Re-test after every major model update
Model updates can drastically reshuffle market shares, so a win measured last quarter can silently evaporate and the win-rate protocol should re-run within a set window on each major release.
Per-platform status
Where a platform documents relevant behavior, its status and source are shown. Undocumented platforms show "unknown" - honest unknowns, never invented.
| Platform | Status | Notes | Source |
|---|---|---|---|
| ChatGPT | Unknown | Not documented by this platform. | - |
| Gemini / Google AI Mode | Unknown | Not documented by this platform. | - |
| Perplexity | Unknown | Not documented by this platform. | - |
| Copilot | Unknown | Not documented by this platform. | - |
| Claude | Unknown | Not documented by this platform. | - |
Evidence and sources
This signal is typed reported (High confidence).
- ACES (arXiv:2508.02630) (opens in new tab) ยท 2026-07-08
How to act on this
Track each engine's current model version and re-run the win-rate protocol within a fixed window whenever a major update lands, comparing against the last baseline.
Related checklist items
Notes
Based on ACES (arXiv:2508.02630), a controlled agent-shopping simulation, not measured real-world sales.