+Tag -> broad life section
project: -> actual project with beginning and end (can be in life section)
+tag -> context of task (where, with whom, etc see GTD)

Good idea for task hierarchy organization in tw:
"I mostly stick with tags, tasks, and subtasks for the structure, with priorities for informal now/soon/eventually scheduling.

Still working out how best to describe broader goals and domains.

Top-level projects kind of work (I have "Site" and "Work" as top-level projects with subprojects for specific projects or narrower domains), but there can be overlap. There's also the "Work is never done" aspect of using top-level projects as domains. It plays hell with your project statistics and keeps that endorphin rush of completion forever out of reach.

I experimented with a UDA for domains. It cluttered things up and was just reinventing tags, poorly.

Current experiment, started about 15 seconds ago: since tags are case-sensitive, use CamelCase to indicate domain: +Work or +Site for example. We'll see how that works out!

And potentially useful tip: tasksh includes a nifty "review" feature for that weekly triage."