Relationship Suggestions

MythTapestry can optionally analyse your content and suggest new relationships between entities — or detect when existing relationships have changed. This feature is off by default and must be enabled in World Settings.

How it works

When you save content that mentions multiple entities, the AI can:

1. Detect new relationships — “Aldric serves the Crown” suggests a “serves” relationship between Aldric and The Crown
2. Detect ended relationships — “Aldric left the Crown’s service” suggests the “serves” relationship has ended

Each suggestion includes the evidence text — the snippet from your writing that triggered it.

Suggestion types

Type	What it means	What confirming does
New	A relationship that doesn’t exist yet	Adds the relationship to your world
End	An existing relationship that the scene says is over	Marks the relationship as ended (sets its end date) — the relationship stays in your records but is no longer active going forward

For an End suggestion, the panel links to the actual existing relationship it thinks has ended, so you can open it and check before confirming.

Triggering suggestions

Relationship detection runs in two ways:

On save (automatic)

When you save a content unit that has confirmed entity mentions and the feature is enabled, detection runs automatically on the full document.

Requirements:

• The feature is enabled in World Settings
• The content unit has at least 2 confirmed entity mentions
• You have available quota for the feature

On demand — from a text selection

You can also run relationship detection on a specific passage without saving:

1. Confirm at least 2 entity links in the text you want to analyse (unconfirmed suggestions don’t count)
2. Select the passage in the editor
3. Right-click → Extract Relationships, or press Ctrl+Shift+R
4. Suggestions appear in the Relationships tab immediately

This is useful when you want to catch relationships in one specific scene without triggering detection across your whole document, or when you want to run detection before you’re ready to save.

Note

The AI uses the relationship types defined in your world to constrain its suggestions. It only suggests relationship types that exist and are valid for the entity type pair involved. This significantly reduces false positives.

Data privacy

What’s sent: The text being analysed (up to 8,000 characters — either the full scene on save, or just the selected passage when triggered from a selection), the list of confirmed entities mentioned in that text, any existing relationships between those entities, and the catalogue of relationship types defined in your world (so the AI knows what types are valid).

What’s NOT sent: Your user identity, world ID, session IDs, or any data beyond what’s needed for relationship detection. Only the specific text being analysed is sent — not your entire content library.

Where it goes: To the AI model provider via OpenRouter, as configured in your model preferences.

Reviewing suggestions

Suggestions appear in the entity’s Relationships tab as pending items. Each suggestion shows:

• The suggested relationship type and direction
• The source and target entities
• A snippet of the text that triggered the suggestion (evidence text)
• The suggestion type (new or end)
• Confirm and Dismiss actions

You can confirm inline for straightforward suggestions, or open the full review modal for more control.

The review modal

Click a suggestion to open the review modal, which lets you adjust the AI’s interpretation before confirming:

Correcting entities — if the AI picked the wrong character or place on either end, you can search for and swap in a different one without dismissing the whole suggestion.

Setting when it started and ended — you can give the relationship a start date and/or an end date at confirmation time, using your world’s own calendar.

Changing the subtype — if the relationship type has subtypes (a family relationship might have subtypes like “parent”, “sibling”, or “spouse”), pick the right one.

Filling in extra fields — some relationship types carry extra details (a contract relationship might have a payment field, for instance). Those appear as form inputs in the modal so you can fill them in while you’re confirming.

Linking to the source scene — you can record which scene this relationship came from. That way, when you look at the relationship later, you can click through to read the moment in your prose where it first showed up.

When a new relationship conflicts with an existing one

Some relationship types only allow one at a time — a character usually only has one active allegiance, for example. If the suggestion you’re confirming would clash with a relationship that already exists, the modal will surface the conflict and ask you what to do with the old one. For each conflict you pick:

• End it — the old relationship gets an end date matching the start of the new one (it stays in your records, just no longer active)
• Delete it — the old relationship is removed entirely. Use this only when the old one was wrong, not just outdated.
• Keep both — confirm the new relationship and leave the existing one untouched. Use this only when you’re sure both should actually be active at once.

You have to make a choice for every conflict before the Confirm button activates — no silent overwrites.

How accurate are the suggestions?

The AI is fenced in two ways:

1. It can only suggest relationship types that exist in your world, and only ones that are valid for the pair of entity types involved.
2. Any suggestion that comes back outside that fence is filtered out before you ever see it.

Even so, review every suggestion — context and figurative language can trip up any model. If the scene says “Aldric is the rock his sister stands on”, the AI can occasionally take that literally. Your eyes are the last line of defence.