Question
How do I practice unique identifiers?
Quick Answer
Open your note system. Search for any term that returns 3+ results with similar titles — 'meeting notes,' 'project plan,' 'ideas,' 'architecture.' For each collision, assign a unique identifier: a date prefix (2026-02-22), a sequential ID (IDEA-047), or a descriptive slug (architecture-decision-event-driven-rewrite).
Rename the note so the identifier is part of the title. Time: 10-15 minutes. Artifact: 3-5 renamed notes with unique, unambiguous identifiers.
Common pitfall: Using titles as identifiers. Titles feel unique when you create them, but they collide over time. You end up with three notes called 'Q4 Planning' and two called 'Onboarding Process.' The collision is invisible until someone links to the wrong one and makes a decision based on outdated information. The fix isn't better titles — it's a separate, stable identifier that never changes even when the title does.
This practice connects to Atomicity and Decomposition — building it as a repeatable habit compounds over time.
Learn more in these lessons
- Unique identifiers prevent confusion
Every distinct idea needs a unique, stable address — without one, you cannot reference it, link to it, or build on it reliably.
Go beyond the answer
This topic is part of Build Your AI Second Brain — a guided sequence of 16 lessons.
After completing this path you will have a capture habit that catches thinking before it decays, notes structured so both you and an AI can retrieve them (atomic, identified, context-rich), a personal knowledge graph AI tools can answer from, and the review loop that keeps the system alive. Ask-don't-search becomes your default.
Start the path →