This would allow shipping Cmdlet's that require Elevation to use, but also allows non-elevated use. Though, we should recommend all cmdlets that require elevation are shipped in their own seperate submodule, bundled as part of the module, not released seperately, to reduce overall maintainence overheads.

This then would enables a sudo like experience via a cross process sudo like experience, wit room to expand this more like sudo in the future.

This then would partially/compeletely resolve comments like this

• https://github.com/PowerShell/PowerSell/issues/26638#issuecomment-3684080588 by @jborean93

Sudo is also a separate command/binary and not something implemented in PowerShell itself. You'll find even if you use the new sudo added in the latest Windows, it only works for new processes and not for elevating a specific PowerShell function/cmdlet. Doing that is just not really possible due to how PowerShell works.

Whilst reducing friction from lack of sudo like experience, like in the above linked issue.

Suggested Direction of Travel (DirOfTrvl) for this,

Discussion (end of Jan) -> RFC (Jan -> April) -> Issue (Created same time as RFC) -> PR (Ideally Aug/September) -> Preview Release (Soon after PR) -> Backports as deemed needed & as soon as reasonably suitable.

Requires review from all Working Groups in some form or another, Language, Engine, Cmdlets, Remoting, Security, DSC, DevEx as well as Core Maintainers, Committee as well as inside and outside partners & the wider community.

We can bypass the need of the issue with linking the PR to RFC & Discussion in the PR title, context & summary & could have bypassed this with an RFC but I'd prefer someone else that feels comfortable take a stab at the RFC, please.