Conversation context and memory are different
A conversation holds the context for one working thread. Memory carries selected context into future work. Dayric may use both to avoid beginning from zero, but they serve different purposes and should remain under your control.
Memory is not a transcript of everything you have said. It should capture durable context that changes how Dayric collaborates with you.
Choose what is worth carrying forward
Useful memory earns its place by improving future judgment. Keep the principles, preferences, and recurring constraints that will remain relevant beyond the current task.
- How you evaluate quality and make recurring tradeoffs
- The audience, product, or body of work you return to often
- Boundaries that should remain consistent across objectives
- Corrections whose underlying principle should guide future work
Review, correct, or remove memory
Inspect remembered context periodically and whenever Dayric applies a preference that no longer fits. Correcting a memory is better than compensating for it repeatedly in new conversations.
- Review the context Dayric is carrying forward.
- Correct details that are inaccurate or too broad.
- Remove context that is temporary, sensitive, or no longer useful.
- Confirm the durable principle you want Dayric to use instead.
Use temporary context deliberately
Not every instruction should become memory. Keep one-time constraints, confidential details, and temporary exceptions inside the active work unless they genuinely belong in future collaboration.