Arno answers:
1: I also feel that all these regular things( which I believe are not projects ) don't really fit into the GTD vocabulary. Usually I work far away and return home for the weekend only. Consequently starting from friday at home I have to go through very regular acitivities with goal 'get ready for monday morning' and during the week target 'get ready to drive home and have a proper weekend'. Friday evenings, usually in a car I do a 'debriefing' session where I speak all my positive and negative experiences into a dictaphone. Many of these issues result in 'rules' to streamline my regular half-weekly tasks like "don't do any shopping after 1100 on saturdays because it's too busy" or "it's good enough to wash this and that twice in a month". My project during this 'debriefing' session is to reduce frequency of regular activities(David Allen doubts it is healthy to check for email permanently) or to drop certain actions completely. From the control perspective the 'check-lists' live in my head alone.
2: It looks to me you have a project called "I need clean context definitions to trust my system' on your mind. Some sort of GTD of GTD level project. Here I would also recommend debriefing sessions. Try to remember in which circumstances things went well or wrong. As a 2nd consequence you narrow the contexts down to reinforce the outcome. Here's an example. Last summer I never found time to read a book I bought. Then I recalled the last time I wanted to read that book. I was on the beach late evening. This is how it got into a 'on-beach' context. You don't need a beach to read the book of course, but for me it helped. The on-the-computer context is usually too general to be of help. I usually have contexts 'mac-online', 'mac-very-long', 'mac-uinterrupted'. If this does not come naturally to you try to remember the situation in which you successfully completed a certain type task. If the result is 'computer-with-cappucino' then that's your new context next time.