Capture without judgment

Capturing without judgment means getting a plan into Composed before deciding whether it deserves to be captured. The thing that stops most people isn’t the friction of typing — the voice input in chapter 2.2 already removed that. It’s an internal editor that intercepts the thought, rules it “too small” or “too obvious” or “I should already be doing this,” and quietly deletes it before it reaches a system. Because Composed captures a spoken sentence in about two seconds, you can get the thought out before the critic catches it.

This is the psychological half of capture, and it’s the half that determines whether the mechanical half ever gets used. You can have the fastest capture in the world and still drop most of your plans — not because capture was hard, but because a filter ran first and decided the plan wasn’t worth the effort. The fix isn’t more discipline. It’s removing the filter from the loop.

The internal editor

The internal editor is the voice that evaluates a thought before you act on it, and for capture it’s the wrong tool at the wrong moment. You remember you meant to call the vet, and before your hand moves, a second thought arrives: “that’s tiny, I’ll just remember it.” Or you think to add “ask the doctor about the prescription,” and the editor says “you really should already have a system for this.” The plan dies in the gap between the first thought and the second.

The editor isn’t malicious — it’s trying to keep your system clean. But cleanliness is the wrong goal at capture time. A plan you didn’t capture isn’t keeping your list tidy; it’s sitting in your head, taking up the exact background attention the whole method exists to free. The Tuesday you decided the “text the babysitter about Friday” reminder was too small to bother with, it didn’t disappear — it nagged at you four more times before Friday, which is far more expensive than the two seconds capturing it would have cost.

Everything is an event

The reframe that disarms the editor is this: in Composed, everything you capture becomes a tracked item — a timed event or a floating thing to do — and neither is a judgment about importance. It’s just a thing with whatever prep it needs. The editor rejects plans because it’s secretly ranking them by priority. But Composed doesn’t ask you to rank. A dentist appointment and “defrost the chicken tonight” are both just things that are coming up, each with whatever small prep they need.

When the unit is “a thing with prep” rather than “a priority worth tracking,” the bar for capturing drops to the floor — which is where it belongs. The AI prep checklist reinforces this: it treats the small captured thing the same as the big one, generating whatever readiness steps fit. There’s no tier where small plans get less. The difference between planning and remembering, covered in this post, is exactly this: planning is putting it in the system; remembering is the expensive thing you do when you didn’t.

The things people don’t capture

The things people don’t capture cluster into three recognizable types, and naming them helps you catch the editor in the act. Testers consistently drop the same categories.

  • The too-small. “Move the laundry,” “reply to that text,” “bring the library books.” Individually trivial, collectively the source of most low-grade mental clutter.
  • The too-obvious. “Pick up the kids,” “take the medication.” Things you “shouldn’t need” a reminder for — until the one day the routine breaks and the obvious thing is the thing you miss.
  • The too-embarrassing. “Schedule the appointment I’ve been avoiding,” “follow up on the thing I dropped.” Plans tangled up with a little shame, which the editor is especially eager to delete.

The plans you’re most reluctant to write down are usually the ones costing you the most attention to keep un-written-down — the mental tab you re-open a dozen times a day. Spoken into Composed in two seconds, the tab closes.

The three-second rule

The three-second rule is the antidote to the editor: capture the thought within three seconds of having it, before the second evaluating thought arrives. The editor needs a beat to engage. If you speak the plan into voice input the instant it surfaces — “call the vet Thursday morning,” “defrost the chicken tonight” — you’ve captured it before the “is this worth it” thought can run.

Three seconds is shorter than the ten-second capture window from chapter 2.1 on purpose. The ten-second rule races forgetting. The three-second rule races the critic — and the critic is faster than forgetting. For busy parents especially, where the day is a stream of tiny interruptible plans, the three-second reflex is what keeps the small stuff from accumulating into background noise.

What happens to small captures

What happens to small captures is the quiet payoff of the whole chapter: they leave your worry-mind the moment they enter the system. A plan you’ve captured stops circling. You’re no longer half-holding “call the vet” in the back of your attention, because the system is holding it now and will surface it at the right time.

This is the difference between a head full of small open loops and a head that’s clear because the loops are closed somewhere you trust. The small captures don’t clutter Composed — they evaporate from you. That’s the trade: a two-second capture in exchange for not carrying the thought.

The practice this week is to catch the editor once. The next time you think “that’s too small to bother adding,” notice the thought, and add it anyway — by voice, in three seconds, before the second thought lands. Do it once and feel the loop close. The editor is a habit, and so is overriding it.

Next: How to trust your planner — the three trust failures, and the mechanism that resolves each.