Episodic Memory
Episodic memory for OpenCoven familiars: remembering concrete past work without flattening it into generic facts.
1 min read
Episodic memory remembers specific events. It answers "what happened?" and "when did we decide that?"
Examples
- A docs PR merged and production deployed.
- A daemon issue was traced to stale socket metadata.
- A release failed because a provider token expired.
- A design decision was made after comparing alternatives.
Relationship to the event log
The session ledger and event log are the raw evidence. Episodic memory is the human-sized summary: enough detail to recover the story, with links or ids back to the source when useful.
Do not replace evidence with vibes. A good episodic note names concrete dates, PRs, commits, commands, or symptoms when they matter.
Promotion
Episodic memory can later become persistent memory when the lesson is durable. For example, "PR #6 deployed" is episodic; "docs PRs need red/green guards before merge" may become persistent process memory.
See Memory search for recall patterns.
Last updated on