*
The framework is a discipline.
If you are going to write about something, it is unlikely to be the only thing you are going to want to write about (i.e., document) ... so, even before you start to write about it, you want to think about its context.
The document you are building is not a document of one or another particular thing, it is a document of that context, which is everything you are thinking about. The question is, where is this particular thing on that context?
And this can be quite tricky.
Places in the context are certain to be related, but those relationships can be quite intricate, even ephemeral.
It turns out part of the purpose of the document is to help you think about those relationships.
But this means you can't know what the relationships are until you have built the framework which connects the thoughts ... and the framework is made out of connections between the thoughts. Our minds need to somehow release this.
My solution was to work out a framework for documenting event - such as my activities - in time. I want to be able to look at a page and see ... this day I did this, then this, then this, and the next day I did this and this.
So this, two hours working on a theory ... It could be placed - I even did so place it - in a category like "theories". (I didn't place it in that category, but one of the general sort.)
There's something dry and difficult about that.
Instead I placed it a page - a link - for what I was doing this morning. I placed that link in a group of links - a category, effectively - things I'm doing today, and that group of links is on a page, which shows, my days, or Crazy Days.
I was careful to do this at the outset ... and ... since doing it ... I have been out and back on this branch, my morning thoughts for this day ... a whole bunch of times. While working on this I've looked at each of these pages maybe dozens of times ... even reading parts of them several times over.
*
