Permission in Realith ​

Permission describes an admissible action over an addressable target and within defined limits.

This is the layer of address-specific admissibility of action.

What permission binds together ​

Permission must bind together:

• the subject;
• the target of the action;
• the set of admissible operations;
• the limits of applicability;
• where needed, term, revocation, delegation, or additional conditions.

That is why permission is always address-specific and contextual.

What permission does not cover ​

Permission by itself does not determine:

• whether the subject is admitted to participation in this environmental regime;
• whether the content is factually disclosed to it;
• whether it has an external or internal basis of right;
• whether the network owes it the needed service profile.

Why permission must not be collapsed with other layers ​

If permission is collapsed into access, technical possibility begins to read as the admissibility of action.

If it is collapsed into right, the architecture loses the distinction between an admissible action and the basis for disposition over the object or its content.

If it is collapsed into admission, participation in the environment becomes a false equivalent of the right to act upon any object inside it.

Short formula ​

Permission answers the question: is a specific action over a specific target admissible in this context.
It does not answer the questions:

• whether the object is disclosed;
• whether a basis of right exists;
• what the network owes as a service.