The compromise I was trying to describe is:
- zones don’t overlap, and can be simple shape (like rectangles).
- each zone allows more than one job to be enabled/disabled.
The end result can be similar though. the union of the shape of the above zones with a single job enabled is sort of equivalent to a single specialized zone for the job. and the corresponding unions for each job types basically form the different potentially overlapping zones in your description.
To use an analogy, assume we are looking at a digital image (made up of pixels of RGB).
One way of looking at it is to see each pixel as one cell, and each can have a value or no value for the colors Red, Green and Blue.
The other way is to look at the whole image as 3 overlapping planes, each plane consisting of only one corresponding colors of a pixel positions.
Your description above, is probably closer to the plane method. While my suggestion was the pixel method. But they could achieve similar thing in the end.
What is pivotal here is probably in the respective perspectives of each of the 2 ways of looking at it:
- specialized zones: can zones overlap?
- multi-function zone: can a zone supports more than one function simultaneously.
If the answer is no (same to both): it just means that some “zone space” will potentially be “wasted”.