[anna]

You put something in the singleton project when it's not part of a project.

Like "Backup laptop" It's not a project. There really is only one step (because I've set up the system already, so it involves clicking a button). I could artificially expand it into a project, or I could call it part of a "computer maintenance" project, but I don't really feel the need to do that right now. I don't like adding complexity unless I need it.

So, enter it. Assign it to the "Work>Singleton" project that I already made. Eventually, all the "Work>Singleton" actions will show up when I'm focussed on "Work" and only viewing "Next Actions." (Right now they show up when viewing "Available").

I think of projects as things that can be actually completed, which is why I don't want a "computer maintenance" project. But if the singleton implementation remains the way it is, I might make goal-oriented groupings (like "Computer maintenance", "Administrative tasks", "Research ideas", etc). That's probably bad GTD.