29 lines
1021 B
Markdown
29 lines
1021 B
Markdown
# Feature Plan: Personal AI Memory (Per Person)
|
|
|
|
## Goal
|
|
Store and manage long-lived person-specific memory for better continuity and assistant quality.
|
|
|
|
## Why This Fits GIA
|
|
- Person-centric data model already exists.
|
|
- Current approvals pattern can gate memory writes.
|
|
|
|
## Scope
|
|
- Memory entries: preferences, commitments, facts, communication style.
|
|
- Confidence/expiry fields and provenance links.
|
|
- Approval-required writes with edit/delete controls.
|
|
|
|
## Implementation
|
|
1. Add memory model linked to `Person` with source references.
|
|
2. Add extraction pipeline (suggested memory from messages).
|
|
3. Add approval queue for memory create/update/delete.
|
|
4. Add retrieval service for compose/AI workspace prompts.
|
|
5. Add memory hygiene jobs: stale decay, contradiction detection.
|
|
|
|
## Acceptance Criteria
|
|
- Every memory has provenance and last-verified timestamp.
|
|
- Unapproved memory never influences generated output.
|
|
- Users can inspect, edit, and purge memory entries.
|
|
|
|
## Out of Scope
|
|
- Cross-user shared memory graph.
|