Atlas Memory¶
Why This Exists¶
This document defines how Atlas uses memory.
Owner¶
The owner is the Chief Product Officer and Enterprise Architect.
Approved Memory Sources¶
- proposal lessons.
- bid task patterns.
- approval history.
- loss feedback.
- submission checklist lessons.
Memory Rules¶
- Memory must preserve source references where possible.
- Memory must not replace current domain state.
- Memory must distinguish fact, interpretation, recommendation, and decision.
- Sensitive memory must follow tenant, privacy, and access rules.
- Memory updates must use approved Intelligence and domain workflows.
flowchart LR
Domain[Domain Events]
Memory[Organizational Memory]
Intelligence[Intelligence]
Professional[Atlas]
Output[Output]
Domain --> Memory
Memory --> Intelligence
Intelligence --> Professional
Professional --> Output