Concept #1: Separating Committed activities from merely Active ones
For my purposes, I’ve defined committed to mean those activities that have been verbally agreed upon with other humans. (That’s probably how it’s already defined in the ResultsManger help docs. But I’m just now getting it.)
Active tasks, then, include the rest of the activities that I’ve planned for myself, self-committed activities, if you will.
As David Allen points out in Getting Things Done, it is important for me to respect the commitments I’ve made to myself, because if I break them, I’m likely feel the same guilt as if I’d broken a commitment with someone else. On the flip side, however, when I’m deciding when to do my work, and what work I can renegotiate, it’s easier to renegotiate commitments I’ve made to myself than those made with others.
Here’s a picture that makes sense to me:

I’m finding that with so many spinning plates, and a propensity to generate too much work for myself, I need to be able to remind myself about what I’ve actually committed to do, versus what I’ve only told myself I plan to do. That’s why I’ve chosen to start drawing a stronger distinction between Committed and Active activities.
By the way, I didn’t come up with the idea of a committed activity, I’m just capitalizing on it. The committed attribute is a standard attribute of a ResultsManager activity, as shown on the following screenshot of the Edit Activity dialog.

Next time, I’ll take a philosophical detour into the difference between using Priority and Committed for organizing my work.