Permissions and capabilities: can it, and may it?
A capability is a kind of operation an environment can provide, such as drawing, storing data, or controlling a device. A permission is a decision about whether a particular program may use an operation within a defined scope.
A classroom may have a printer, but that does not mean every program should print a thousand pages. Availability and permission answer different questions.
Scope keeps a request small
A scope describes the boundary of access. “This project’s saved data” is narrower than “every file on the computer.” Ask for what the task needs, and understand what a request would allow before accepting it.
Pliro’s saved-data functions work through an app-private store. That means storage belongs to the app identity, rather than giving source code an arbitrary disk filename to open. The host applies the supported storage rules and limits.
Missing or refused
Unavailable means the needed feature is absent in that environment. Denied means a policy or permission decision refuses the requested use. Neither should silently become fake success.
The exact controls depend on the feature and host; this article does not promise a permission dialog for every current Pliro call. The feature’s reference and host guide describe what is implemented.
An entitlement says which product operations an account may use. It is separate from a program’s permission to access a device or private data.