Help

Changes

Rewrite one canon fact and see which facts and documents it may touch, up to 2 hops away, before anything in canon changes.

Where Sidebar → Changes, or Propose change… on a fact in Canon

A change proposal in The Ashbell Pass sample: the bell rule now and as proposed, with its possible review impact listing related canon facts to re-check.

What you see

  1. Propose a changeThree steps: pick a fact, write the new version, check the impact.
  2. ProposalsTabs To decide, Applied, Rejected or reverted and All.
  3. Proposal cardThe fact now and as proposed, and why.
  4. Possible review impactDocuments of every kind (scenes or chapters, lore, quests, dialogue, recordings; grouped by kind) and related canon facts the change may touch, by hop, each with its path, source quotes and rationale. Export it as JSON, CSV or Markdown.
  5. Re-review tasksAfter a change is applied: one task per affected document, with progress. Open in Tasks shows them.

Propose a change

  1. Under Which fact?, search canon and pick the fact.
  2. Under What should it say?, write the New version, or select Start from current wording and edit it.
  3. Fill in Why change it? (required).
  4. Select Analyze impact; the proposal and its impact appear under Proposals.

Accept or reject a proposal

  1. Select Show impact and read the documents and facts it may touch.
  2. Fill in Why (required) under Decide.
  3. Select Accept & apply to write the new version to canon and keep the old one as superseded, or Reject to leave canon as it is.

Revert an applied change

  1. Open the Applied tab and find the change.
  2. Select Revert this change… and fill in Why revert? (required).
  3. Select Revert to original; its open re-review tasks close as not needed.

How impact works

  • It looks only at accepted canon, at most 2 hops from the changed fact: 1 hop is tied directly to it, 2 hops go through a related fact.
  • Every item carries its path, its evidence and a rationale.
  • An empty result reads “no impact found”: nothing was found within 2 hops, which is not a guarantee that nothing is affected.
  • If a merge changes the names involved after the analysis ran, the proposal says Impact out of date. and can’t be accepted until you select Re-run analysis. See Change impact.

Three different things

A change proposal (a rewrite you decide on), a conflict candidate (a possible clash on the Conflicts page) and a possible review impact (what a change may touch) are separate. Accepting a change applies it; a conflict decision never edits canon.

Who can do what

Viewer
Read proposals, their impact and history, and export the impact list.
Editor, admin, owner
Propose changes, accept and apply, reject, revert and re-run the analysis.

Roles are per studio. Roles and permissions has the full list.