*protoTyping

One way to define Context in the GTD sense is "a place you need to be, or something you need to have with you to be able to do that action". But I have found that context can also be about a consistent set of actions or projects surrounding a unified theme.

Take personal finances for example. Most of the actions and projects will happen in the @HomeOffice. But the specifics of personal finance have their own actions separate and distinct from most of the other actions that might take place in the @HomeOffice context.

So, while most of my @HomeOffice actions are finance related, I nevertheless transfered all tasks and projects having to do strictly with personal finances into their own context - @Finance. But first, I had to create the new Context -- a multistep process that begins with the creation of a new prototype.

I created the prototype *Finance within the parent container note Prototype and placed it in logical order beneath the *HomeOffice prototype. As is my habit, I used the singular form - "*Finance" making it easier to remember should I need to add the term manually to any note's attribute from within Explorer view. All my prototypes are written in the singular; *Item, Action, Project etc. You might also notice the notes named "-" which serves as handy-dandy separator in the prototype pulldowns of the note naming tool.

Next, I set up the various attributes for the *Finance prototype.

-IsPrototype=true; this provides for the inheritance of attributes for all the notes that link to this prototype note

-Prototype=Prototype; allows one to globally change the prototype notes if needed by linking to a prototype note called, yes; Prototype. It's a bit like a master style sheet. Change the color of the note Prototype and all the linked notes will change accordingly.

-OnAdd= Prototype=*Finance; the children of any @Finance notes that call *Finance their prototype note will also use the *Finance prototype automatically. Automation is good and I try to make as much happen automatically as I possibly can.

-Action=True; this is my standard GOTCHA! Because the agent will look for Action Items - notes where Action is true - it is essential that the prototype has Action=true. When your first test notes don't end up in the new agent, check the prototype to see that Action is true.

Now with the Prototype note set, all that needs to be done is set up the Agent to collect the new notes in their new Contexts. I'll break that down in Part II -- Ready Set Action!

A Shed with a View

Tinderbox Help

Understanding Attributes

ATPM - Deep Tinderbox

Mark Bernstein

GTD on the Web

The David Allen Company

My Toolbox