Makes sense to move it here! I only asked there, as the answer might have something to do with beacons and how you ‘tag’ for them, in your token scheme.
I have indeed read the existing discussions. My remaining question is about where in your token scheme you systematically denote the entry is for a project. Such that, when searching through or visually scoping the collection, you can quickly pull up a list of all active projects.
I am curious, because in other software paradigms, for new projects (ex. making a stone carving), a user creates a new database or folder, names it after the subject (‘Windsor Road house entrance’), and dumps everything related to it in that database/folder. In that paradigm, projects are paramount and always visually and cognitively prominent; everything is hierarchically tucked away within them.
Your ICFS obviously denotes a different approach. I understand the linking to reference materials from the project’s “library card” entry. But I suppose I am trying to fully understand your token scheme, through this important issue of demarcating which entries are projects.
I first thought that you would assign a number in your ‘secondary numerical axis’ to projects: e.g. C1.2.stone-carving Windsor Road, where the ‘2’ would denote ‘this is a Creative.Private.Project.stone-carving for Windsor Rd’.
But in light of the other forum post — where you said a beacon entry is noted by the tag ‘Thread’ (I1.1.Thread) — perhaps the Token + Description would be something like C1.4.Project stone-carving for Windsor Rd (= Creative.Private.Unfinished.Project + Description)?
If I missed an existing answer, I’d be grateful to be pointed to it!