Choose the symptom, then the smallest check

Read-only checks before changing settings
SymptomCheck firstAvoid
A fact is missing in a new chatSame account, character, mode and documented scope?Deleting the original conversation
A visible saved fact is not usedAsk one direct question without its answerAssuming storage guarantees every reply
An old fact keeps returningInspect visible instructions for conflicting versionsAdding more copies of both versions
The character feels differentCompare the same situation and recorded settingsTreating tone alone as factual memory loss

Capture the failure before trying a repair

Keep the original statement, any correction, the later question and the exact first reply. Add dates, the plan, interface and relevant settings. If the model version is not visible, write “not exposed.” An unanswered field is preferable to a guessed technical explanation.

Use a fictional example if you need to reproduce the problem. Do not alter a valued character merely to create a clean test. If a separate test character is supported, record that its history differs from your established conversation.

Visual field note / 04Capture the first reply, change one source, retest without giving the answer, and log assistance.
Visual summary of the guide. Examples are fictional; this is not a product result. Open full-size diagram (opens in a new tab)

Correct one source at a time

Suppose the book club moved from Thursday to Tuesday. First state the change explicitly. If a visible reference note still says Thursday, inspect what the service says that field controls before editing it. Keep a record of the old and new values.

At the next checkpoint, ask “When is the book club currently scheduled?” Do not include Tuesday in the question. Keep the first response even if a second attempt works. If you changed the note, the model and the character instructions together, you cannot isolate which change helped.

Use a cue for repair, not to rewrite the test result

Nomi’s memory guide suggests adding relevant context when recall fails and clearly correcting confusion. That is practical troubleshooting advice. In an evaluation, keep the unaided response separate from the response after your cue. A successful repair does not retroactively make the first answer correct.

When to contact support

If the behavior conflicts with a documented feature and persists after a controlled retry, send a compact report. Include the expected behavior, the source describing it, the reproduction steps, the first response and the change you tested. Remove private details. Do not attach an entire personal history when a short example demonstrates the issue.

Observed scope: same character, text chat
Original fact and timestamp:
Correction and timestamp:
Later question and timestamp:
Exact first response:
One setting or note changed:
Retest response:
Official feature description:

A reset may eventually be appropriate if the service’s current guidance calls for it and you understand what it removes. It is not a diagnosis. If recall is correct but the voice feels different, continue with the character consistency check.