Honestly? We need not a successor of FHS but of filesystems, who are intimately tied package managers and installers. Zfs timidly start the change, with IPS (Image Package System) and BE (Boot Environments, as zfs clones), and we need to go much beyond that instead of wasting resources keeping up an '80s model like some do from btrfs to stratis.

We need:

- query-able storage, because search&narrow is the current way of accessing information and collecting/transcluding data is the way to go;

- easy storage management, the "rampant layer violation" of zfs we really need;

- integration of such storage to the software stack, from the OS to single packages, it's a nonsense having to "spread" archives in a taxonomy to deploy them or downloading archives to be unpacked as well for updates when we have send-able filesystems (zfs send of snapthots) and binary diff (from a snapshot "tagged version" of a fs-package to another, sent over internet).

Unfortunately we need operation people together with devs and nowadays operation is nearly disappeared. Devs alone can't understand what we need, they can't go beyond their desktops in a mass large enough to avoid a positive evolution.

Who is "we?" I certainly don't need those things. If you need to add a bunch of complexity for your use case then feel free, but for most of us it's unnecessary.

> - easy storage management, the "rampant layer violation" of zfs we really need;

Except in zfs you have to think if you really want that device in that pool or that vdev. I use btrfs, slow and kinda unsafe, specifically because you just specify raid1c2/raid1c3/raid1c4 and it kind of survives c-1 dead disks (until you run out of disk space and everything goes to flames).

> - integration of such storage to the software stack, from the OS to single packages, it's a nonsense having to "spread" archives in a taxonomy to deploy them or downloading archives to be unpacked as well for updates when we have send-able filesystems (zfs send of snapthots) and binary diff (from a snapshot "tagged version" of a fs-package to another, sent over internet).

We (kinda, for some very generous definitions of) have that in composefs? But I still sense even with that, you still want some resemblance of sanity in your indivual layers.