Uncertain about atomicity during capture? Write it now, split it during review
When unable to determine if a note contains one idea or two, write it as-is during capture, then return during a dedicated review session to attempt decomposition without the pressure of real-time capture.
Why This Is a Rule
Capture and refinement are two different cognitive operations that compete for the same resources. During capture, speed matters most — the insight is decaying and you need to externalize it before the context evaporates. Pausing to analyze whether your note is truly atomic introduces friction that can cause you to lose the insight entirely, or worse, capture a degraded version because you spent 30 seconds on structural analysis instead of on content.
The atomicity decision can almost always be deferred to review without loss. A compound note captured quickly preserves all the content. The structural decision — one idea or two? — can be made later during a dedicated review session when you have time, context is no longer urgently decaying, and you can think carefully about boundaries between ideas.
This rule resolves the tension between the atomicity principle (one idea per note) and the speed-of-capture principle (capture now, refine later) by assigning each to the appropriate phase: speed wins during capture, atomicity wins during review.
When This Fires
- Capturing an insight and uncertain whether it's one compound idea or two separate ones
- Writing quickly during a meeting, conversation, or reading session
- Feeling friction during capture because you're trying to get the structure perfect
- Any time perfectionism about note structure is slowing down capture
Common Failure Mode
Never returning to review. The compound note gets captured and then sits in your system permanently, because "review" is scheduled "later" and later never comes. The rule only works if you have a regular review practice. Without it, deferred atomicity decisions accumulate as structural debt that progressively degrades your knowledge base.
The Protocol
During capture: (1) If atomicity is unclear, write the note as-is — compound is fine. Prioritize completeness and speed. (2) Tag it with a review marker (e.g., #needs-split or a dedicated inbox). During review (weekly or bi-weekly): (3) Open notes tagged for review. (4) For each, attempt decomposition: can this be split into atomic notes, each standing alone? (5) If yes, split and link. If genuinely one idea, remove the review marker. The temporal separation preserves capture speed while ensuring structural quality through a dedicated refinement pass.