Take a look at the readme...

...DATA LOSS may occur and it may kill your cat.

😭😭🤧

I've thought a lot about stuff like this and this is pretty cool but this basically looks like just a tagging system for files, which already exists in many ways. A true graph based file system wouldn't just be an overlay over a directory tree. Would love to see some kinda filesystem dedicated to graph representation, where each file is a node with multiple edges.

Why stop at a tag-based file manager? Why not a tag-based filesystem?

That kind of storage might somewhat work for media files and simple tags if you only view the files in the tag-aware file manager but what about other applications and files?

If the path of a file changes every time you add a tag or remove one that means the path of files is very unstable so you can't e.g. reopen the last used files in other applications easily. I also don't think this scales to the billions of files on a modern system. And of course any files required by an application to be in a specific place will be screwed up completely by this.

Maybe the tag directories should be hard links to the actual files instead?

I don't see how the tag => file path will be workable. As you add and remove tags, your actual file system is going to go strait to hell. Dear god I don't want to think about what that would be like to browse from the terminal