What are the advantages of the system being a single file?

As a UX researcher who dabbles in Linux, I'm impressed by the ideas in this project.

I'm curious though, why does it matter if the system is a single file? There are distros that do pretty much this, like Puppy and Quirky, but I'm not sure what the advantages are apart from being able to drop in files to update the system which isn't something the user should have to do.

The ostree model in [Fedora Silverblue ](https://fedoramagazine.org/what-is-silverblue/) seems like a good approach. Like Android, macOS Catalina, and Chrome OS, the system image is read-only so the user can't accidentally break their system.

Additionally, Chrome OS and Android 11 support ["seamless" A/B updates](https://source.android.com/devices/tech/ota/ab), which I think is worth considering as well.

No files, tests, or entry points are named. Start by reading the discussion and the linked material on ostree and A/B updates, then identify the project's current single-file rationale and whether a concrete change is expected. Done would require a documented decision or an agreed, scoped implementation plan.

Written by the indexing model from the issue text.