Interactive graph
Atomic Notes
Table of Contents
One clear claim per note - split before the ands pile up.
Key Concept
- One claim I would say out loud - too many ands, split it.
- Rule of thumb: one thing I would cite in conversation - “why middle-click saves tab chaos” is atomic; “browser tips and meeting notes” is not.
- Small notes stack like Lego blocks - linked, not merged.
- Link with
[[wikilinks]]; let Maps of Content and backlinks do the organizing. - If I need headings inside one file, I probably need two notes.
- Faith parallel: Let Your Yes Be Yes - say one plain thing; let your yes be yes.
Level 1 - Recognize
An atomic note holds one claim you would say out loud - too many ands means split the file.
Level 2 - Explain
Like one LEGO brick with one shape - “call coach” is one note; “call coach and buy shoes and fix bike” is three.
Level 3 - Use
Before you save, ask what one sentence you would cite in conversation - mixed topics mean two notes, not one.
Level 4 - Connect
Small files create more links and upkeep, but mixed claims hide relationships and make reuse harder - split when a heading or another and marks a second idea.
Level 5 - Create
Split a broad draft into single-claim notes, link the claims with [[wikilinks]], and add a Maps of Content hub only when the cluster needs a doorway.
Examples
- “Why my basketball shoes live by the door” is one claim - I would say it alone at carpool.
- “Where we meet if the elevator is out” is one claim; “elevator outage and parking-gate codes” is two - split and wikilink.
Note Relationships
| Relationship | Wikilink | Reason |
|---|---|---|
| alternative | Mind Mapping | Single file per idea vs one bubble map when splitting early |
| contradicts | Maps of Content | when I bury claims inside a hub instead of one file per idea |
| extends | Let Your Yes Be Yes | One plain claim per note - same yes-means-yes discipline |
| extends | PKM | One-claim notes are the Lego blocks PKM stacks and links |
