TurenOS project memory stores durable facts, decisions, observations, and reusable lessons that should survive beyond one conversation.
What belongs in memory
- Stable architecture decisions
- User or project preferences
- Persistent constraints
- Diagnosed failure causes
- Reusable operational knowledge
Do not store routine progress, transient state, secrets, or information already maintained in source-controlled documentation.
Agents can search memories, read a selected record, add a new record, supersede an outdated record, or forget a record when you explicitly request deletion.
Memories are project-scoped. Search before making a decision that may already have established context.
Source context versus memory
Use source-controlled docs for public contracts and team-wide procedures. Use project memory for compact context that affects future sessions but does not belong in the repository.
Memory is durable application data, not a secret manager. Store credentials in the Secret Vault or your operating system’s credential store.
