== Problem: Activity Permissions == #2009

  Rainbow needs to grok activity permissions.

Situation:

  We've got a preliminary example of a how required permissions might be
  specified by a bundle.

  Caveat: this attempt was designed while only thinking about code-carrying
  bundles, so its reasoning may be invalid for data-only bundles and or
  extended bundles.

Plan:

  Start locking down containers, then accrete permissions and their semantics
  on a couple of sample activities.


Followup:

 F1. We need to think hard about how error handling is going to interact with
 permissions. How on earth is a user going to find out that their activity
 isn't working because of a permissions misconfiguration?