Skip to content

Relationships and the Family Tree

A Relationship is a typed link between two Entities: “sister of”, “sworn to”, “owes a debt to”. Where a Reference says these two are connected, a Relationship says how.

Open Relationships from a Codex (or from inside a Manuscript) to see the graph: Entities as nodes, Relationships as labelled edges. Click through to any Entity; add, edit, or remove Relationships from either end.

The map earns its keep as the cast grows — loyalties, rivalries, and chains of obligation are graph problems, and reading them as a graph beats reading them as forty character files.

trove · Relationship Map
The Relationship Map — characters and locations as nodes with kinship and other typed edges, and the relationship list alongside

Family relationships get their own view: a genealogy layout with marriages, children, and the connecting lines you’d draw on paper. Build it from the same Relationship data — parentage and marriage are just typed Relationships — and the tree assembles itself.

Dynasties, inheritance plots, and “wait, are they cousins?” all live here.

trove · Family tree
A character's family tree — marriage and parentage lines drawn from Relationship data

Relationships are records in the Codex, stored as plain files like everything else. No database; delete the app and the connections are still readable.

See also: Entity, Maps, Canvas.