@publicvoit a bit late, but this is a comment for your post
First, a bit of a sidenote, why don't I use diqus: besides the obvious privacy obvious "oh no evil company" bla bla, I use Twitter to log in, and then I have no way of knowing if there was a reply, unless I have a reminder to go back and check the commet. Mastodon is a place I'm logged into way more often on the desktop, and always on the phone, so there's that. OK! Moving on...
I'm of the camp of using keywords for a project, the one you repeatedly said in this post and the post that connects to it that you don't like.
From what I gather though, this is mostly due to two things:
first, there are projects that remain "open" even if their subtasks are all done. Maybe you'll get to it later, maybe you're stuck (for now), maybe it's just something without a pending actionable item all the time.
second, you want to be able to find these projects, and when a project is marked as done, it looks like any other tasks you marked as done. You could use tags (which you are) but it's more the point that if you just use a keyword it's not enough, and if you need to use tags, it's not "purely" a keyword
(also by the way totally agree on not using keywords for people who may do parts of the projects, this is what tags are for, at least for me).
OK, now I can actually bring up my point:
to sum it up, I'm "cruel" about my project. A project, to me, is either "active" (that's my keyword) or done. Done can be cancelled (keyword) or done (keyword).
This forces me to minimize what a project is, its definition, so I can go through it. My agenda stuck project configuration marks "Active" keywords that do not have any "TODO" keyword under them. It means exactly what it is: a project is stuck if I don't have an actionable plsn of what I'm doing next.
the other constraint is time. To me, a project is something that has a beginning and an end.
Anything that is too long or might be too long is not a project, but a category. It starts its way as a parent tree in one of my weekly files, and if it keeps growing week in and out, month in and out, I eventually make it its own org file.
while technically not needed, it's helpful to see something like "photography.org" in my personal folder, as I know it's an ongoing thing.
When a project is done, in order to find it I could use a search that will grab the "Active" keyword inside already done projects since I keep keyword changes logged (for done or cancelled) in my weekly files. But I never needed to.
reason for that is that any big project usually gets referenced in my personal journal and/or wiki, if it's something I want to repeat in the future. For the wiki, I re-right it in a 1-2-3 way that links to the old project with unique IDs as reference.
This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!