This isn't a response to the parent commenter's point, right? They were describing how many projects have items where a resource easily fits within the scope of N different categories, at which point they become max N steps away from it, not max 2 steps.
1. This is much, much less likely with the enforced limits on categorization in the post.
2. No - you are still 2 steps away. Make a choice about where that item lives. If it's shared across many categories, maybe you really need a distinct category like "Ambiguous" or "Shared"
You misunderstand. The max N steps are at the point of recall, not categorization decision.
> you want a document, you are two steps away from it in an easy to find way
This is not how people work in general. This kind of thing might be OK for institution for taxonomy like collections.
I think there's a good way forward that uses typical hierarchical Johnny.Decimal filesystems, with an overlay filesystem with tags that can update the tags every so often based on the content in the files. Obviously letting the user have a hand in this via a TUI/gui would be helpful for choosing tags for which they're comfortable.
Unfortunately I haven't settled on a good filesystem with tags (how to do this with ZFS?) or how to interact with it as a network filesystem served to many different OS (cifs with tags?).
Or the old-school method, a community of people with tagging powers and a few moderators to do sanity checks.
They created this so the hierarchy is unambiguous (as much as possible), you want a document, you are two steps away from it in an easy to find way.
tag systems have far too much maintenance and adding a new tag is almost impossible to do exhaustively so you have a lot of partial tags.