How to use
- Start after the general winner order already looks believable enough to defend in prose.
- Describe the scope, scenario spread, and override mode, then read the matrix as a comparison across cases, not as a single trace.
- Use the output to decide whether the winner changes are intentional before audit or export turns them into production rules.
Compare winner flips across theme, state, and platform scenarios
This page fills the gap between “one token trace is explainable” and “the same role behaves acceptably across multiple scenarios.”
How to choose between nearby pages
Use Token Fallback Map when the open question is still the general winner order. Use Token Resolution Debugger when one concrete token path still needs a local explanation. Use Color Token Audit or Color Token Diff when the scenario logic is already settled and the remaining question is set-wide quality or before/after rollout impact. Use this page in between, when you need to compare where one role changes winners across multiple scenarios.
FAQ
What does this page compare?
It compares how one token role resolves across multiple theme, state, and platform scenarios, then counts winner flips and shadowed reserve layers.
When should I use this instead of Token Resolution Debugger?
Use Token Resolution Debugger when one concrete token path needs a local explanation. Use this page after that, when the remaining question is how winners change across multiple scenarios.
When should I use this instead of Token Fallback Map?
Use Token Fallback Map when the open question is the general winner order. Use this page after that, when the order is mostly accepted and you want to see where the winner flips across theme, state, or platform combinations.
What is stored in the share URL?
The share URL stores component scope, theme-set mode, state-set mode, platform-set mode, override mode, alias depth, prefix, and role.