The more fundamental question is whether filenames are under control of the user or the system. The answer today is "both": there's blessed paths /System/Librar

The more fundamental question is whether filenames are under control of the user or the system. The answer today is "both": there's blessed paths /System/Library... and non-blessed paths like ~/Documents/Pokemon.txt. Addressing this properly means reifying that distinction: making apps always be explicit about whether they're working with the user's or the filesystem's view of a file. This distinction is important for other reasons, too. Should this file be indexed for search? Should it store an access time to support features like "recently opened"? On the other side, we want to know which blessed paths "belong" to which system application or service so we can sync them, protect access to them, and uninstall them with their owners. Maybe the user-visible document store should be a separate mechanism entirely from low-level app/service data persistence.