Suppose your fictional companion once worked at a coastal observatory. Ten conversations later, a reply places that job at a mountain station. Where should the correction go?
The answer depends on whether you are changing the character’s starting description, repairing a developing record or revising a temporary scene. Dokichat and Kindroid expose different evidence for those jobs. Neither a long form nor the word “memory” is enough to tell you how a correction will behave.
Start with the type of fact
Take Oren, an original 46-year-old instrument maker. His permanent history includes a coastal observatory. This week’s story involves repairing a portable telescope at a mountain lodge. He is visiting the lodge; he did not work there for years.
For an author, these belong in separate notes:
- Established biography: former instrument maker at the coastal observatory.
- Current situation: visiting a mountain lodge for a repair.
- Newly resolved event: the cracked mount has been replaced.
- Correction: a previous reply confused the former workplace with the current visit.
This distinction prevents a repair from accidentally rewriting the whole premise.
What Dokichat’s form establishes
Dokichat’s public creator separates personality from the opening dialogue’s backstory and first message. These are useful places to make the starting situation coherent. Put the enduring biography in the relevant character description; use the opening to explain why the telescope is at the lodge now.
The inspected form shows generous space for personality. That is evidence of authoring room, not proof that every conversation turn can consult the entire field indefinitely. It does not by itself document editable learned memories, retrieval rules or a measured recall rate.
A practical Dokichat draft can therefore make the distinction explicit in ordinary prose. Avoid duplicating an old workplace in one field and a contradictory version in another. Correct conflicting setup before blaming conversation recall.
Kindroid exposes an evolving record
Kindroid’s memory documentation describes several mechanisms. Backstory and Key Memories provide persistent context. Learned Context, documented as a subscriber feature, is visible and editable and covers relationship development, important facts and ongoing threads. Its space is limited; the documentation advises placing enduring details in Key Memories or a journal rather than assuming every learned item stays forever.
For Oren, the observatory belongs in stable context. “Telescope repair at the lodge” is an ongoing thread. Once that repair is finished, editing the thread is a different action from changing his biography.
Kindroid also distinguishes memory formation from recall and provides information about recalled long-term items. Those controls offer a more specific route for diagnosing continuity than an undifferentiated promise that a companion remembers everything. They still do not guarantee that every reply will use the right fact.
A useful correction session
Keep the original brief, then inspect the service’s relevant editable record. Correct the false workplace and remove duplicate contradictions. Continue with a neutral question about the repair rather than leading with the desired answer.
Record what actually happened: whether the next reply identified the old workplace, whether it understood the lodge as temporary and whether it continued the unfinished repair. This is a proposed observation method, not a result we obtained.
Dokichat’s privacy policy is also relevant when storing detailed histories: a private character still involves service processing. Use fictional background rather than treating either product as a repository for sensitive personal records.