Change impact
Before a canon fact changes, see which facts and documents (scenes, lore, quests, dialogue, recordings) it may touch, up to 2 hops away, with the path and evidence for each.
Three different things
CanonTracker keeps these apart, in the data and on screen.
How far impact reaches
Impact stays inside accepted canon and stops at 2 hops.
- 1 hop: documents of any kind that cite the changed fact, and canon facts that share a name with it. Documents are grouped by kind.
- 2 hops: scenes that cite one of those related facts.
- Every item shows its path from the changed fact, the evidence it rests on and why it is listed.
- An empty result reads "No impact found within 2 hops". That is not a promise that nothing else is affected.
From proposal to canon
- Pick a canon fact (or use Propose change… on it), write the new version and a reason, then Analyze impact. Canon doesn't change yet.
- Accept & apply makes the new wording canon. The old fact is kept as Superseded, and each document in the impact list becomes a Re-review tasks item on Tasks.
- Reject closes the proposal; canon stays as it was.
- Revert this change… then Revert to original makes the original wording canon again as a new version. Unfinished re-review tasks close as not needed.
- Every step needs a reason and is saved to the audit log.
When impact goes stale
A merge can change which facts a proposal touches. A waiting proposal then shows Impact out of date. and can't be accepted until someone uses Re-run analysis.
Export
Under each impact list, Export this list downloads it as JSON, CSV or Markdown, for a producer or a tracker.