Resolve a trusted principal to permissions owned by the host.
The resolver receives no request body or caller-provided context. Human
roles and automated identity/provenance are already carried by the validated
principal, so both kinds use the same server-side boundary without treating
an automated principal's compatibility role projection as authority.
A throw, rejection, or malformed result fails closed: it denies an agent
that declares requiredPermissions, and it costs any other run its
permission projection — so a connector that declares requiredPermissions
denies inside that run. Both outcomes audit the generic reason permission resolution failed; the underlying error is never re-exported, so log
failures inside the resolver itself.
Resolve a trusted principal to permissions owned by the host.
The resolver receives no request body or caller-provided context. Human roles and automated identity/provenance are already carried by the validated principal, so both kinds use the same server-side boundary without treating an automated principal's compatibility role projection as authority.
A throw, rejection, or malformed result fails closed: it denies an agent that declares
requiredPermissions, and it costs any other run its permission projection — so a connector that declaresrequiredPermissionsdenies inside that run. Both outcomes audit the generic reasonpermission resolution failed; the underlying error is never re-exported, so log failures inside the resolver itself.