The fact alone looks portable
Memory might return an exact sentence from an earlier conversation. The consumer can quote it flawlessly. Yet the sentence may have been a draft, a joke, another persona's interpretation, or a plan that was later revised. Correct retrieval is not correct understanding.
The problem grows when information crosses systems. A planning event and a completion event can concern the same meeting without meaning the same thing. If a consumer sees only the meeting text, it may tell Jim the work happened when Memory recorded merely an intention.
Context changes how a fact may be used
Consider the sentence 'I will send the draft tomorrow.' A search can retrieve it accurately. To answer whether it was sent, the consumer needs speaker, date, status, linked later action and contrary evidence. If no sending record is found, say ‘I found a promise, but cannot confirm delivery,’ not ‘it was never sent.’
PHS's M16B admission design separates retrieval from authorized prompt use and calls for ownership, status and provenance. The Memory-Engram provisional specification describes retrieval/admission and interpretive lineage. These are design and patent claims, not proof that every current consumer receives complete context.
Pause here: What would you need to know before turning this retrieved sentence into a present-tense claim?
Send evidence with its limits
Memory should return speaker, date, owner, status, qualification and lineage. The consumer must judge this audience and present purpose, and may say evidence is insufficient rather than treating an old sentence as present truth.
Correct data becomes useful knowledge through interpretation that remains answerable to its source. The consumer's job is not to invent certainty, and the provider's job is not finished when it returns a familiar phrase.
My answer: The consumer needs provenance, ownership, temporal status, purpose and lineage alongside data. Correct retrieval alone does not supply the meaning of the evidence.