We clarified the boundary between memory and retrieval. Memory can stabilize follow-ups, but it should not silently become evidence unless the system can inspect and explain its use.
Boundary rules
- Conversation state can help interpret the query.
- Retrieved evidence remains separate from remembered context.
- Answer synthesis should not treat unresolved memory as proof.
- Memory writes must be intentional and bounded.
Design constraint
Memory is useful only when it is inspectable. If memory cannot be reviewed, corrected, or scoped, it becomes another hidden prompt input.
Trade-off
Using memory can reduce recomputation and improve follow-up handling. It also increases the risk of stale or irrelevant context. The runtime keeps that trade-off explicit.