A continuing fictional relationship needs enough context to make an ordinary exchange understandable. It does not need a full biography repeated at the beginning of every conversation.
SoulChat and Nomi describe different ways that context can persist. The useful question is which facts define the relationship and which merely explain what is happening today.
Write the relationship in three sentences
Our original adult characters are two independent booksellers who share a weekly reading event. They enjoy discussing cover design. They prefer friendly disagreement to automatic agreement.
A compact relationship note could establish:
- They collaborate on the weekly event but run separate shops.
- One favors experimental covers; the other likes restrained typography.
- Each can disagree and choose their own actions.
This prevents “we work together” from becoming “we own the same business” or “we always have the same taste.” Specific distinctions do more than a long list of affectionate adjectives.
Today’s event needs a separate sentence: a guest author has asked to change the reading time. That circumstance should change when the decision is resolved.
Nomi’s named context sections
Nomi’s Backstory+ documentation separates enduring background, current roleplay, preferences and boundaries, among other sections. This gives the writer an explicit place to separate the booksellers’ relationship from the guest author’s temporary request.
A useful background explains who the participants are to each other. The current roleplay explains the schedule problem. Preferences describe how they like to discuss choices. Boundaries preserve a limit on what either participant may assume about the reader.
These are our proposed notes. The documentation describes a context mechanism; it does not prove that any amount of writing will be followed perfectly.
SoulChat’s retention framing
SoulChat’s current Profile interface also exposes My Character Card: name, personality, relationship with the character, and background story. Its explanatory text says every character will know this information. That is materially different from waiting for a conversation-derived memory to form. We verified the public frontend text, not a saved card or every character’s response.
For this example, “I run a separate bookshop and collaborate on reading events” can be a reusable self-description if you want it applied across companions. “We accepted the guest author’s new time today” belongs in this particular conversation. Do not put a relationship that applies to only one companion into a card described as shared with every character.
SoulChat’s privacy policy describes conversation processing and a limited recent memory window for free accounts, with extended retention for VIP. Its public product presents readable memories and controls for editing or forgetting them.
This supports treating a continuing conversation as something to review, not a permanent archive that never needs correction. It does not establish a one-to-one equivalent to every Nomi section.
If the booksellers’ relationship is described incorrectly, correct the actual recorded fact where the interface allows. Do not silently accommodate the wrong premise by writing a new fictional history around it.
A return note should move the scene forward
After a pause, a useful message could mention that the guest author’s new time has been accepted and ask which display to prepare. It closes one thread and opens another.
Compare that with a full retelling of how the shops were founded, every past event and all previous conversations. The larger account may obscure the one decision that matters now.
Choose Nomi when its documented context sections fit the way you organize an ongoing relationship. SoulChat’s described memories can suit reviewing facts derived from conversation. In either case, keep a small independent original brief and judge continuity through replies you actually observe, rather than through the emotional tone of a marketing promise.