docs(FN-2097): clarify layered memory layout and legacy fallback semantics
- Update memory architecture and contributing docs to describe .fusion/memory/ as the canonical layered workspace - Reframe .fusion/memory.md references as a deprecated legacy fallback used only for migration/alias compatibility - Expand the memory plugin contract with explicit layered layout, migration behavior, and invariant language - Align settings reference memory-insight file descriptions with the canonical long-term memory model
This commit is contained in:
@@ -410,7 +410,8 @@ Fusion can automatically extract insights from project memory and prune transien
|
||||
|
||||
| File | Description |
|
||||
|------|-------------|
|
||||
| `.fusion/memory/MEMORY.md` | Working memory (updated when pruning is applied and validated) |
|
||||
| `.fusion/memory/MEMORY.md` | Long-term memory (updated when pruning is applied and validated) |
|
||||
| `.fusion/memory.md` | Deprecated legacy fallback (migration compatibility only; not canonical storage) |
|
||||
| `.fusion/memory-insights.md` | Long-term insights distilled from working memory |
|
||||
| `.fusion/memory-audit.md` | Human-readable audit report after each extraction |
|
||||
|
||||
|
||||
Reference in New Issue
Block a user