I've always operated with this principle: A project task with no context is "inactive". Assigning a context IS the simple mechanism to mark it active. FWIW, I've always used @waiting as a context, since most @waiting's start life as some other context... it is a simple matter of changing the context. If a software package can't do this I look elsewhere. Which, I just realized, means I've never used software that could be called "a true GTD app". YMMV.
Originally Posted by Folke