I'm familiar with fossil albeit not the technical details. Mine is not a version control system and it doesn't actually store files. Rather, it maintains an a

I'm familiar with fossil albeit not the technical details. Mine is not a version control system and it doesn't actually store files. Rather, it maintains an association between filenames (absolute paths) and sets of tags. There are some tradeoffs with such a scheme, but my priorities were that it should be non-invasive and keep filesystem access to a bare minimum. Something that you can use to organize a cluttered nfs-mounted NAS without actually moving the files (in case you later decide the system is not for you, everything is in the same place as before you started.) It's basically a relational 'card catalogue' (https://en.wikipedia.org/wiki/Library_catalog https://en.wikipedia.org/wiki/Library_catalog)