> For the complete documentation index, see [llms.txt](https://wiki.secrets.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.secrets.ai/lorebooks/relationship.md).

# Relationship

PREMIUM and ULTIMATE feature. Record relationship dynamics, boundaries, pet names, and meaningful promises.

{% hint style="info" %}
**Available on PREMIUM and ULTIMATE.** Lorebooks are included for all subscribers on these [plans](/get-started/subscription-tiers-and-limits.md). On FREE, your companions use the [Memory System](/get-started/memory-system.md).
{% endhint %}

Use **Relationship** for the ongoing dynamic between people: who they are to each other, how they interact, and what they have agreed. It answers **“What is true about this relationship?”**

It can describe friendship, family, teamwork, romance, rivalry, or another established connection. Write the relationship you intend to maintain in this book.

<figure><img src="https://3286776735-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9ACKOAU4nFWSXPeE2B4s%2Fuploads%2Fgit-blob-3a5aa4a7238ed7b22338e593deb8a84080a4557b%2Frelationship.png?alt=media" alt="Fictional Relationship entry for Mira and Rowan describing friendship, teasing, a pet name, and a promise"><figcaption><p>A relationship entry makes the participants and their shared expectations explicit.</p></figcaption></figure>

## What belongs here

| Detail                                | Example                                                     |
| ------------------------------------- | ----------------------------------------------------------- |
| Established connection                | Mira and Rowan are longtime friends and mapmaking partners. |
| Interaction style                     | They enjoy gentle teasing and quiet conversations.          |
| A boundary or preference between them | Public embarrassment is unwelcome.                          |
| A name used within the relationship   | Mira calls Rowan “North Star” in private.                   |
| A meaningful ongoing agreement        | They ask before changing each other's maps.                 |
| Current relationship state            | They are rebuilding trust after a disagreement.             |

Name both people when the book contains several relationships. “They trust each other” is harder to interpret than “Mira and Rowan trust each other's judgment about the route.”

## Create a Relationship entry

1. Open **Relationship** and select **+ New**.
2. Choose a title naming the people or the specific dynamic.
3. Describe the relationship's main subjects in the short description.
4. Write a small set of current, established statements in Content.
5. Select **Save**.

**Title:** `Mira and Rowan`

**Description:** `Mira and Rowan, friendship, teasing, mapmaking promise`

**Content:**

```
- Mira and Rowan are longtime friends and mapmaking partners.
- Gentle teasing is welcome; public embarrassment is not.
- Mira calls Rowan “North Star” in private.
- They promised to ask before changing each other's maps.
```

## Separate current status from hopes and possibilities

If two characters have only discussed becoming partners, do not write that they already are partners. Use wording that preserves uncertainty:

> Mira and Rowan have discussed working together permanently but have not decided yet.

If a decision is still pending, also add the outstanding conversation to **Open threads**. When they decide, update this entry and close that thread.

Similarly, describe an interaction preference directly: “Rowan prefers a calm response during disagreements” is more useful than “Mira always knows the perfect thing to say.”

## Which section should hold a promise?

* **Relationship:** an ongoing agreement, such as asking before editing each other's maps.
* **Open threads:** a specific promised action that has not happened, such as returning a borrowed chart.
* **Chronicle:** the scene in which the promise was made or fulfilled.

You can use more than one section when each records a different part of the situation. Avoid copying the same long account into all three.

## Update the dynamic as it changes

When the relationship develops, edit the existing entry so it describes the present. Keep a past disagreement in Chronicle if it remains useful history; do not leave it phrased as an ongoing conflict after reconciliation.

Review suggested changes carefully. A single playful exchange may not mean the entire relationship has changed. Accept a new label, pet name, or commitment only when it matches what you want established.

## Keep different storylines separate

If Mira and Rowan are strangers in one story and old friends in another, use [separate books](/lorebooks/managing-books.md). A chat using a shared book receives the same relationship information as the other chats using it.

Pin a concise relationship entry when its dynamic matters across the conversation. Lock settled boundaries or agreements if you want changes to remain under your control. Locking does not stop you from editing the entry yourself.