Capture
Table of Contents
Saves what resonates into one trusted inbox, then empties weekly.
Key Concept
- Friction kills capture when saving takes more than one quick move.
- One inbox from phone to desktop, weekly process - same as The Trusted Inbox.
- Skip it unless action or citation would follow later.
- Resonance is the filter, not FOMO.
Level 1 - Recognize
Capture is saving what resonates into one trusted inbox before the spark fades.
Level 2 - Explain
A fast, single path keeps friction from killing the idea and delays sorting until review.
Level 3 - Use
Scribble the idea now in one inbox, then process it during the weekly review.
Level 4 - Connect
Capture preserves sparks but creates clutter when nothing useful will follow; filter by likely action or citation and keep sorting separate.
Level 5 - Create
Design a capture path that works across your devices, then shorten it until a spark can survive the trip.
Examples
- A play tweak hits during cooldown and I scribble it on my wristband before the locker room noise eats it - one inbox, file it Sunday when the spark is safe.
- On the jeepney my kid says something I want to remember and I scribble it on a receipt before the station noise eats it - one pocket notebook, no sorting yet.
Note Relationships
| Relationship | Wikilink | Reason |
|---|---|---|
| contradicts | Signal vs Noise | when save first and filter later |
| extends | Frictionless Capture | Zero-friction inbox is the habit this note assumes |
| extends | PKM | Capture is the first PKM move - save what hits you into one inbox |
| implements | The Trusted Inbox | One inbox habit carries capture into something you will empty |



