Something happens
A promise, injury, secret, relationship shift, new place or world fact is established in play.
How continuity works
How MelumiyaChat remembers without flattening the story.
A long-running roleplay needs more than a larger context window. MelumiyaChat separates remembered experience, world truth and current story state so different kinds of continuity can evolve without becoming one undifferentiated block.
Memory ownershipWorld canonProvenanceConflict protection
The continuity pipeline
Conversation becomes durable story state.
MelumiyaChat is designed to promote meaningful facts out of the transcript and into inspectable structures without treating every sentence as equally important.
The fact is noticed
Meaningful state is identified without interrupting the roleplay screen.
Memory or canon?
The system decides whether this belongs to a character's remembered experience, the World Bible, or both.
Merge, don't multiply
Duplicates are merged and evolving AI-derived state can be updated instead of creating endless copies.
User canon wins
If an AI-detected fact conflicts with user-authored canon, the conflict should be reviewable rather than silently replacing it.
The next scene knows
Relevant memory and world state can be brought back into later RP so history keeps exerting pressure on the present.
Two kinds of truth
Memory is not the same thing as world canon.
This distinction matters whenever characters can lie, misunderstand, forget, keep secrets or know different pieces of the same event.
What is true in the world
Canon can track locations, factions, objects, rules, relationship state, secrets, physical continuity and story timeline.
- The attack was ordered by the family accountant.
- The burner phone is in Adrian's jacket.
- Mara's shoulder is still injured.
What a specific person carries
A memory can belong to particular characters and preserve who was involved, when, where, importance, emotional weight and current relevance.
- Adrian remembers promising to stay.
- Mara remembers the promise differently.
- Neither of them yet knows who ordered the attack.
Provenance
Important state should have a trail.
Auto-detected facts are designed to retain where they came from so an editor can understand why something became part of memory or canon.
Source
Whether the item was user-created, seeded by a scenario or detected from roleplay.
Original context
The RP message or event that established the fact can remain associated with the stored item.
State evolution
Old states can resolve or be superseded without erasing the history that led there.
Contradiction review
User-written canon remains authoritative when auto-detection disagrees.