[Nickydigit]

I like that approach of tagging files to create meaningful filtering and organization a lot. How many times did I fail to find what I was looking for in a file tree only because I was off by one branch at one part of my pathing, when the file would have been "fine" being available in both paths...

In a knowledge base approach that also mean that information should not be bound to a file but available through tagging and references to a lot more workspaces / subjects.

Ex : a technical documentation that would be filled with all the relevant code extracts / third party documentation / custom notes available in the knowledge base, automatically fetched based on the tags and information entered in the tech stack or the header of the documentation.