How to use
- Start after token ownership, dependency, conflict, and winner order already look believable enough to keep.
- Pick the change type, target layer, scope, and depth you want to model.
- Read the output as a blast-radius estimate before refactor, diff review, or export.
Simulate blast radius before changing one source
This page fills the gap between “I know the dependency map” and “I know what will likely move first if I actually change the token.”
How to choose between nearby pages
Use Token Dependency Graph when the open question is still who depends on one shared source. Use Token Conflict Checker when the open problem is still conflict hotspots or redundant overrides. Use this page after those steps, when you want a quick estimate of what changes first if the source is renamed, replaced, or removed. Use Token Rollout Checklist after this page when the blast radius already looks believable and the remaining question is what must be reviewed before release.
FAQ
What does this page simulate?
It estimates which token branches and component surfaces are likely to change first when one source token is renamed, replaced, or removed.
When should I use this instead of Token Dependency Graph?
Use Token Dependency Graph when the open question is still who depends on one shared source. Use this page after that, when the remaining question is what changes first if you actually modify the source.
When should I use this instead of Token Conflict Checker?
Use Token Conflict Checker when you still need to find conflicts or redundant overrides. Use this page when conflict review is believable enough and you want to model refactor impact.
What is stored in the share URL?
The share URL stores change type, layer, theme branch, state branch, component scope, depth limit, prefix, and role.