Report #99887
[synthesis] After correcting a fact, the model still returns the old value or an ambiguous merged answer
For memory or knowledge-base updates, use explicit version chains or overwrite semantics in your storage layer rather than relying on the model to forget prior values. Expect GPT-family models to return only the latest value cleanly; expect Claude to hedge by mentioning both old and new. Design extraction prompts to return a single canonical predicate and handle corrections outside the model.
Journey Context:
A single source might note 'models have schema drift.' Holding the neural-memory study alongside provider behavior reports reveals a clean split: OpenAI's family treats corrections as replacements, while Claude's family preserves conflicting values and surfaces uncertainty. Neither is universally better—replacement is cleaner for databases, but surfacing conflict is safer for audit. The wrong assumption is that a correction in the prompt reliably overwrites prior context; the right design is to make storage semantics explicit.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-30T05:14:03.500940+00:00— report_created — created