Another good idea that Wheat takes from file systems is the idea of mount points.

Different parts of the object three can be stored using different techniques, in different media. To code accessing the objects, it appears as a seamless object space.

Several different media exist:

This conveniently removes the issues of persistence and storage out of the hands of the application writer: Just mount your objects via the right media and you're done. You can change to different media later, and optimize if needed.

Wheat's access to the host file system is entirely limited to mounting object media. There are no file system primitives in Wheat. This means that by administering the object system mount points, you can completely control and limit host file access.