Subject scope
Authority can be associated with an identified user, service, worker, or agent rather than assumed globally.
Security / Permissions
Authority should be explicit and narrow.
ILAIOS is being engineered around least-privilege permissions that can constrain who or what may invoke a capability, against which target, and under what conditions.
Permission boundaries
Scope capability before execution.
Action scope
Permission to read, generate, modify, deploy, approve, or delete can be treated as distinct capabilities.
Resource scope
Allowed targets can be narrowed to specific projects, data, services, or operational boundaries.
Revocability
Authority should be capable of being withdrawn without redesigning the workflow that previously relied on it.
Fail closed
Missing authority should stop the action.
Sensitive execution paths are intended to reject ambiguous or absent permission rather than infer consent from context.