Protocol
Search before creating a second canonical note
Duplicate knowledge creates maintenance forks.
When it fits
- The same concept appears under slightly different titles across projects.
When to avoid it
- Duplication can be useful for immutable snapshots or independent contexts; name why the copies must diverge.
Why it matters
Before creating a durable note, run a quick search using the concept and likely aliases. If a canonical entry exists, update or link it and keep project-specific context separate. Create a new canonical object only when the claim, scope or job is genuinely different.
Steps
- Does a canonical note already exist?
- Is this new information or new context?
- Can the project note link to shared knowledge?
- Would two copies drift independently?
An example
Three projects link to one current 'order block migration checks' note while each keeps its own project-specific values.
Check your result
Shared knowledge has one maintained canonical version unless scopes genuinely differ.
Keep this limit in mind
- Duplication can be useful for immutable snapshots or independent contexts; name why the copies must diverge.
Connected ideas
Use beforeUse aliases for names that change but the knowledge object does notUseful with
Merge duplicates when you encounter them, not in a heroic cleanup month
Evidence and sources
Supports
Personal information management research frames the job as a lifecycle of acquiring or creating, keeping, organizing, maintaining, finding or re-finding, using and distributing information in support of future needs.
The lifecycle is descriptive and does not prescribe one folder, tagging or note-taking system.
Personal Information Management · Abstract and overview
Supports
A 2026 systematic review treats personal information management on desktop and mobile devices as affected by multiple human and technological factors rather than a single organization technique.
Available summary does not justify ranking specific PIM tools or methods.