Warm-up, Ritual, and Transition

Build a 10-minute warm-up protocol that gets you 80% of the way to flow before you start the work proper. Build a transition protocol for switching between modes — client work, your own product (if you run one), family, hobby — without leaking attention residue across modes. Internalize the 90-minute ultradian cycle as the natural unit of work. The warm-up is the boot sequence with cache warming. A cold-boot Rails app handles the first ten requests slower than the steady-state because the autoloader, the connection pool, the Bootsnap cache, and the in-memory caches are all populating in real time. Production apps don't ship this way; they boot fully, warm critical caches, and then take traffic. The 10-minute warm-up is the same architecture applied to your own cognition. The transition ritual is the connection-pool cleanup between requests. If you don't release a database connection cleanly at the end of one request, the next request gets a degraded pool. If you don't shut down client mode cleanly before opening own-product mode, the next session gets a degraded attention pool. Newport's "complete + record + release" is connection.close. You're not done with the previous work until you've explicitly released it. The 90-minute ultradian cycle is the garbage-collection pause. The mind, like a long-running process, accumulates allocations that have to be reclaimed periodically. Trying to skip the pause produces a system that runs longer between GC events but pauses dramatically when forced. Two 90-minute blocks with a 20-minute true rest between them outperforms three hours of forced continuous work, in the same way that periodic small GC outperforms one catastrophic full GC.