New Slice on Security and Integrity

These ideas are not new; my friends will see no novelty here. Few real platforms conform to these ideas however.

This replaces another file of the same name that I wrote about 2006.

I don’t know where this fits and perhaps that is why I have not written it down before. A software platform is some combination of hardware and software that allows a developer who would create some new appication to build upon extant technologies (hardware and software) rather than reinventing the computer world. The platform may also provide a convenient physical body to carry about; even if separate physical devices for each of 100 apps would fit in my pocket, I couldn’t find the one I needed when I needed it, and they certainly need to share a screen. Besides the apps need to talk to each other to do their legitimate job.

Current platforms host a variety of applications, ‘apps’ here, but do not control interactions between these very well. We consider here the nature component interactions.

For this note I do not distinguish between ‘system function’ and ‘other apps’. Instead I want to track what an app must, by its task rely on to achieve its purpose and what it must rely on by the nature of the platform. I also consider that if app X is vulnerable to app Y, or the ‘installer’ or uninstaller of Y for its correct operation then X ‘unnecessarily’ relies on Y.

For an app to be correct:

There are two styles of argument that some app does the right thing