Injecting Events into the Trail

The Goo Trail records the actions or events that you do to Things in your environment. But what about incoming events that arrive from your environment? Server down. High load on cluster. Girlfriend on phone.

I spend about half my time making Things happen and the other half responding to "events".

Ideally I don't want to be buffeted by incoming events: "Chill out everybody! Form an orderly queue and please take note of my Care[O]Meter." Some Things deservedly fall below my threshold of "care" (e.g., spam email) while others deservedly displace everything else I was doing (e.g., server has gone down).

I want the Care[O]Meter to act as a lens on incoming events. Focusing my mind's eye on the important stuff while maximising my productivity and minimising the number of context switches I need to make during the day as I process useless events (e.g., spam email).