Attention Is Freed Only on Statement and Clarity
Creating a fixed-window ritual that instantiates and assigns every open loop a state, so none of them has to poll for attention during the week.
My experience:
Figured out this on a Sunday, which is generally my most scattered or anticipation-computing day for what I haven't closed during the week, and for what comes the next week.
The objective of this ritual is to prune and conclude every worktree that is past due or dormant, and give executional clarity and datetime to those that are latent. This way, and by allocating a specific time of the day to do this dedicatedly, we prevent their recall in unwanted or inconvenient moments, therefore allowing fluid uninterrupted attention and efficient allostasis.
Premise
- An open loop consumes background attention until it has either a resolution or a scheduled place in time.
- Loops without resolution or place in time recall themselves at random, reliably during deep work, not during idle time.
- Therefore: attention is not freed by finishing things. It's freed by stating things.
Every loop leaves the session as (state, timestamp, next physical action and/or defined outcome). "Later" is not a state. Make sure you're answering: How does this start? / What's the set of conditions that make this done?
Failure modes
- Executing during the ritual -> Route only.
- Infinite triage -> the window is fixed; unrouted remainder auto-parks to next week.
Open loops consume attention until they are stated, not until they are finished. A fixed recurring window routes rather than executes: every open worktree gets exactly one state plus a timestamp and either a next physical action or a defined outcome, one answering how it starts, the other how it ends. Exit condition is zero unstated loops, not zero loops, and it holds only if the rest of the week captures without processing.