[Discussion] What should trigger Dream CE?

[CaralHsi]

Dream CE currently starts from a simple signal: newly added memories accumulate until Dream can be triggered.

This is intentionally minimal, but a real memory system may need richer trigger signals.

Possible trigger signals

• Newness: many new memories have been added.
• Conflict: new memory contradicts or challenges existing memory.
• Frequency: similar topics or failures appear repeatedly.
• Feedback: user feedback shows an answer was wrong, useful, or unsatisfying.
• Recall hit patterns: certain memories are repeatedly retrieved.
• Unresolved goals: a task or user intention remains incomplete.
• Emotional or importance signal: some memory appears unusually important.

Questions

• What should trigger a Dream run?
• Should Dream run on a schedule, on thresholds, or only manually?
• Should different signal types produce different motive types?
• How should we rank which memories are worth dreaming about?
• How do we avoid running Dream too often?
• Should triggers be per user, per cube, per session, or per topic?
• What signals have you seen in your own agent or memory systems?

Current code direction

Current Dream CE has:

• DreamSignalStore
• DreamSignalSnapshot
• MotiveType
• cube-level trigger API

The code is designed to allow richer signal producers later.

Desired outcome

We want to identify the most useful first signal types to implement. Strong proposals may become implementation issues, such as:

• add conflict signal producer,
• add feedback signal producer,
• add frequency-based Dream trigger,
• add session/topic-level triggers.