2.0 KiB
2.0 KiB
| id | type | title | tags | importance | confidence | created | updated | relations | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| e301095c-7d4c-45d8-8352-9491e4ad6603 | decision | Overlap Memories Duplicated to Both Target Graphs During Migration |
|
0.7 | 0.8 | 2026-03-01T22:16:56.955400+00:00 | 2026-03-01T22:17:17.438067+00:00 |
|
Decision: Copy Overlap Memories to Multiple Target Graphs
Context
During migration of memories from default graph to named project graphs, some memories are tagged for multiple projects (e.g., both major-domo and paper-dynasty).
Decision
Overlap memories are COPIED (not moved) to each matching target graph. They remain in the default graph until all migrations complete, then the --cleanup-overlaps flag removes them from default.
Rationale
- Preserves memory context in both project graphs where it's relevant
- Avoids data loss if migration is interrupted partway through
- Keeps default graph clean after all targets are confirmed populated
Implementation Details
- Overlap tracking stored in
_migration_overlaps.json - A memory is an overlap if it matches tag criteria for 2+ target graphs
- Cleanup step verifies presence in all target graphs before deleting from default