> An issue I didn't see raised, probably because it is not
> relevant to the design as given, is "execute only" access...
There isn't really a difference between execute only and read only from a
security perspective -- both constitute reads by the CPU. Preventing a user
from examining your code can be done by interposing a process boundary, though
execute only probably does have advantages in reducing certain classes of
programming errors.