Using the canon graph

The canon graph is a visual way to inspect narrative structure.

It helps you see how entities, places, events, objects, and claims connect.

What the graph is good for

Use the graph to:

find central characters and locations;
inspect relationships around one entity;
spot duplicate or suspicious nodes;
notice isolated entities with no evidence;
identify dense clusters that may need review;
understand why a continuity item matters.

What the graph is not

The graph is not proof. A node or edge may come from weak evidence, ambiguous extraction, or an unresolved review item.

Always inspect the underlying evidence before treating a graph relationship as stable canon.

A practical graph review

Start with one major character.

Ask:

Are their aliases correct?
Are they linked to the right locations?
Are their relationships directional and meaningful?
Are key events connected?
Which edges lack strong evidence?
Which nodes look like duplicates?

Then move to the next major entity.

Dense graphs

A dense graph can mean the story is richly connected. It can also mean Arc created too many weak relationships.

If the graph feels overwhelming, filter by entity type, chapter, relationship type, or review state where the product supports it. Otherwise, return to the review queue and resolve the highest-impact items first.

Using graph insights

Graph review should lead to action:

merge duplicate entities;
reject unsupported relationships;
add notes to the story bible;
revise manuscript inconsistencies;
preserve unresolved ambiguity where the story intends it.