I think tokenmaxxing is completely backwards, like good ol' KLOCs (thanks, for always sharing, DT). I'm still experimenting, so this will inevitably change. Right now, though, I am pleased with tracking my Job and Task count.
Tasks are the fundamental unit of definable, useful work in GalexC.
Jobs are dispatched, asynchronous, fully automated jobs that act primarily on Tasks (these exclude workstation terminal sessions).
A Task can have children and grandchildren, but no more nesting than that is allowed. Each task is almost always iterated upon - typically with a combination of my iterative design process and multi-agent debates (roundtables, adversarial, synthesizers, single casts). This has produced incredible results in this context - steady feature development based on known needs, improved ability to derive business useful output and perform business useful work (for example, update websites and collateral, prepare for meetings, transcribe and learn from my meetings, directly version and edit Google Docs, and much more). I, along with GalexC, will try to write about as much of it as I can (the good, the bad, and the ugly).