Keep project identity, provenance, and context packs separate; review proposed merges before approval.
Last reviewed:
About this guide
This guide was prepared with AI assistance using the project’s public documentation. It does not claim testing on every device or independent human review. Project publisher: AmirSina Zamanian.
Sources are listed at the end. Use the project repository to report an error or suggest a correction. Report an issue
⌕
Search runs on this device.
On this page
Why is a project name not enough?
Two folders can share a name while representing different projects, and two tools can operate on one path. Review the project map before sync to avoid transferring the wrong decision. The public release uses path, repository identity, and content markers to propose identity; a proposal is not a substitute for review.
First map one project from two tools and inspect its roots, tools, and merge reason. Add a second project separately. Output identifiers must be distinguishable; when inputs share a name, choose distinct names and recheck identifiers before applying. Until identity ambiguity is resolved, a context pack is not a safe basis for decisions.
Inspect each project’s separate pack in 09-Exports. Pick a known decision and verify its project and source. Compare created, updated, unchanged, and removed states with expected changes. An unchanged status alone does not establish the correctness of all memory content; continue reviewing decisions and provenance.
Stop the receiving tool before it applies changes, set aside the wrong pack, and inspect the map and selected sources. Do not delete history or the Vault to conceal the issue. After an approved correction, repeat sync and verification. This guide does not claim multi-user security isolation; the product is designed for one local user.