Unify Modularity and Security Mechanisms

When I design code I arrange for separation of authority for two reasons:

in support of the modularity that programming stylists have sought for 40 years
Protection against malfeasance
Intermediate problems such as code written by someone with a different understanding of an interface.

In Keykos I have been able to use the same mechanisms for both but in Java I am advised to use separate tools in Java to accomplish these two ends; this despite Java’s support of the fundamental mechanisms that supported both in Keykos. I have happily unified the tools in my head and now I am asked to separate the tasks and learn two tool sets for the artificially separated goals.