Sequence gaps during refactoring are specs for new notes…
When refactoring reveals that notes in a sequence jump or break, treat those gaps as specifications for new atoms to write rather than as sequence failures.
When This Fires
- Arranging notes into a sequence for an argument, presentation, or essay
- Reviewing a note chain and noticing a logical jump between two connected notes
- During any refactoring session where the structure of relationships becomes visible
- When a reader (or AI) points out that your argument "skips a step"
Common Failure Mode
Forcing connections between existing notes with vague transitions: "This leads to..." or "Relatedly..." These transitions feel like they connect the notes but actually conceal the gap. If you can't write a specific note for the missing step, the connection is a handwave, not a bridge. The gap remains — it's just hidden behind a transition phrase.
The Protocol
When notes in a sequence jump: (1) Mark the gap explicitly: "Between [Note A] and [Note C], the reasoning skips [describe what's missing]." (2) Write the missing note: explain the mechanism, the step, or the connection that's absent. (3) Insert the new note into the sequence. (4) Verify: does the train of thought now flow without jumps? If it still jumps, there's another gap — repeat. The completed sequence, with all gaps filled, is a more rigorous argument than anything you could have produced by forcing connections.