Kubestro » Server

A module extends the platform itself, so the platform has to be sure it is talking to the module the operator installed and not to something else on the same machine, and recorded history has to show when a module acted on its own rather than on someone's behalf.

A module gets its identity from being installed, with nothing for an operator to copy or store, and its channel to the platform is protected. Work a module does on its own initiative, such as a scheduled task, is attributed to that module by name. A module is trusted at the level of any other installed software: it declares the permissions of its own namespace and its own actions are not second-guessed.