Now / Soon / Reference — spring cleaning for your brain that will actually work Monday morning

Last week we mapped the friction. This week we make one of the biggest leverage moves in digital spring cleaning: a file system your real brain can maintain. Not your aspirational brain. Not your "if I had six uninterrupted hours" brain. Your Tuesday-at-2:13 PM brain.

One of the biggest lessons from last year's Digital Spring Cleaning series was this: people do not need more folders. They need fewer decisions. So today we're using a refreshed version of the 3-Folder Rule and connecting it to the Grit Framework prompts in this issue. Keep it simple, keep it searchable, keep it sustainable.

In my own systems, too many folder choices is usually where momentum dies.

The 3-Folder Rule is not about perfection. It is about giving every active thing in your life a clear home with the fewest possible decisions, and what I would do first if I was given a new machine for work.

Top level:

That's enough.

Inside each folder, you can add subfolders as needed, but the top level stays stable. The key is that when you save a file, you can answer one question quickly:

Do I need this right now, soon, or mostly as reference?

If you can answer that, you can file it in seconds.

Most systems fail because they ask your brain to classify at too high a resolution:

Those are useful distinctions later. In capture mode, they're exhausting.

Start broad. Refine only when the folder gets crowded enough to justify it.

If your system makes you pause and overthink every save, it is too expensive for real life.

Pick one naming convention and use it everywhere for docs you create:

YYYY-MM-DD-topic-short-context

Examples:

Why this works:

No elegant prefix taxonomy required. Just consistency.
Plus, if you are using AI Agents in your files with Claude Cowork, or Cursor (like I do) you can add naming rules for your Agents to update when you’re just in the flow and may not fully follow your own rules. If you create rules to follow for your Agents to follow, they can help pick up any leftover mess left through your week. But you need a naming convention, and a top-level file system first.

Want to take an elevator to more than 3 folders? This is the Cursor Notes repo I used as a template for my "brain” which is a 10 folder system with an Index.

This is where the Grit Framework (adapted from Duckworth's Grit) becomes practical:

Use the “System Friction Score” prompts in this issue to evaluate your current setup. If your score is high, your system is too expensive to use.

Small wins compound. You're not rebuilding your whole digital life in one sitting.

I use Sparkle on my Mac—it automatically organizes files in Desktop, Documents, and Downloads using AI (Every’s write-up explains the whole approach: Introducing Sparkle). It was a big part of what finally got me to stop spreading data across a dozen half-finished systems and consolidate onto one external hard drive last year: fewer mystery piles, fewer “I’ll merge these later” duplicates.

Sparkle sorts into buckets like Recents, AI Library (auto structure for older files), and Manual Library (you decide what it should not touch). The best folder system still benefits from fast retrieval—after things have a sane home, I’m not hunting through sedimentary screenshot layers just to find last week’s photo download for Canva.

Privacy check-in (read the fine print): Every states that Sparkle uses filenames to organize (sent to their servers and GPT-4), and that file contents are not transmitted or stored—worth reading their security section before you opt in. If cloud-assisted sorting is a no for your threat model, stick with the 3-Folder Rule manually; sovereignty first.

Sparkle ships with an Every subscription (trial available); pricing and bundle details are on their site. Not on Mac, or skipping Sparkle? This week’s sprint still works: use your built-in file search (Spotlight on Mac, search from the taskbar on Windows) to open things in Now without clicking through nested trees.

This week's prompt:

What file naming habit keeps tripping you up right now?

Reply and tell me where your system breaks down: duplicate versions, unclear titles, downloads pile, collaborative docs chaos. I may feature anonymized patterns next week so we can normalize this and solve it together.

Fire Horse energy can tempt us into dramatic overhauls. Sometimes that works. Often it creates a second mess.

This week, channel that energy into independence:

You don't need a system that impresses strangers. You need a system you can come back to after disruption.

🔥 Carry this forward: if your system doesn't support your return, it's not resilient yet.

The Pythoness Perspective is free, always. If it's useful to you, here are ways to support the work: