I've been wondering this too: for us, UUIDs are super opaque. But for an agent, two UUIDs are distinct as day and night. Is the best filesystem just blob storage S3 style with good indexes, and a bit of context on where everything lives?

One thing directories solve: they're great grouping mechanisms. "All the Q3 stuff lives in this directory"

I bet we move towards a world where files are just UUIDs, then directory structures get created on demand, like tags.

▲

para_parolu 4 hours ago | parent | next [-]

Filepath is just unique name that model can identify easily and understand grouping. Uuid solves nothing but requires another mapping from file to short description.

	▲	JoeAltmaier 3 hours ago \| parent [-]
		UUID solve oh so very, very much. You can have several versions of the same set of data object at once - an entire source set for a build, all the names duplicate but tagged with 'revision' so they can be distinguished. Hard to do that without a UUID at root, to use for unique identification of the particular 'particle' of the particular data set.

▲

JoeAltmaier 3 hours ago | parent | prev [-]

Or, have to "Q" attribute and ask the file store for "Q=3"

All good.