The way it is currently written, it seems like it's possible for a lower-level admin user to create a page that the Administrator doesn't have the ability to view. Of course, the Administrator could just change it back, but it still doesn't make any sense that the Administrator could be locked out of anything in the first place. There should be an exception made in the DisplayDrivers to guarantee that the Administrator is always marked as a valid role for a given ContentItem and that their access is not prohibited.
This is especially important for #14 which would enable a user on the backend to prevent an Administrator from even editing the content item.
The way it is currently written, it seems like it's possible for a lower-level admin user to create a page that the Administrator doesn't have the ability to view. Of course, the Administrator could just change it back, but it still doesn't make any sense that the Administrator could be locked out of anything in the first place. There should be an exception made in the DisplayDrivers to guarantee that the Administrator is always marked as a valid role for a given ContentItem and that their access is not prohibited.
This is especially important for #14 which would enable a user on the backend to prevent an Administrator from even editing the content item.