How to use
- Start after token ownership, winner order, and conflict review already look believable enough to keep.
- Describe the source layer, scenario spread, alias depth, and how far downstream you want to inspect.
- Read the output as a dependency map before rename, replace, diff, or export work.
Map upstream aliases and downstream fan-out
This page fills the gap between “I understand the winner” and “I know what else breaks if I change the source.”
How to choose between nearby pages
Use Token Resolution Debugger when one token path still needs a local explanation. Use Token Conflict Checker when the open question is still conflict hotspots or redundant overrides. Use this page after those steps, when the unresolved question is which downstream branches depend on one shared source before a refactor or export. Once the dependency spread already looks believable and the remaining question is which themes, states, or layers flip first after the change, move to Token Impact Simulator.
FAQ
What does this page show?
It shows an upstream alias chain and the downstream token scenarios that depend on the same source token across theme, state, and platform branches.
When should I use this instead of Token Conflict Checker?
Use Token Conflict Checker when the open question is where conflicts or redundant overrides still pile up. Use this page after that, when the remaining question is which downstream branches depend on one shared source before you rename or replace it.
When should I use this instead of Token Resolution Debugger?
Use Token Resolution Debugger when one concrete token path still needs a local explanation. Use this page when the path is understandable, but you need a wider dependency map before refactoring.
What is stored in the share URL?
The share URL stores source layer, component scope, theme set, state set, platform set, alias depth, graph depth, prefix, and role.