It’s pretty distant now, but I did imagine it from a user perspective to be something like a folder structure except you can “tag along” as you go, so that you can find the files from your subjective chain of association rather than remembering how the project is set up. Say to reach the file;

• /project/year/keyword 1/keyword 2/file
• /keyword 2/year/project/keyword 3/file

Consequently, you could have all relevant files collected or filtered depending on how you set up your paths like searching a database rather than keep track of different data structures of different department needs and such.

So you could call it a mind map of sorts.

My entry level experiments were with just “tags” (the keywords) but I imagined a file system that would incorporate everything filesystem like permissions, creation/modification dates, and next gen like file history, integration with custom content parsing and version control systems and stuff that are partially reality today with COW filesystems.