@glyph Sorry but this won't work. Some requirements are incompatible with each other.
There are distros that runs with a read-only rootfs from a CD and distros with daily upgrades. There are distros for 128 Go servers and distros for 64 Mo wifi routers. There are distros for machines that constantly sleep to preserve batteries and distros for servers with UPS that shall never go down. There are hardened distros and tinkerer-friendly distros. There are privacy-preserving distros, corporate-friendly remotely-managed distros and no-administration auto-upgrading distros. There are move-fast-break-compatibility distros and distros backward compatible with 10 years old software.
If you don't account for all of them then your unified solution will not gain broad adoption.
There are distros that runs with a read-only rootfs from a CD and distros with daily upgrades. There are distros for 128 Go servers and distros for 64 Mo wifi routers. There are distros for machines that constantly sleep to preserve batteries and distros for servers with UPS that shall never go down. There are hardened distros and tinkerer-friendly distros. There are privacy-preserving distros, corporate-friendly remotely-managed distros and no-administration auto-upgrading distros. There are move-fast-break-compatibility distros and distros backward compatible with 10 years old software.
If you don't account for all of them then your unified solution will not gain broad adoption.