Jobs are executed in a dynamic module; modules have isolated sessionstate, and share access to globals. PowerShell closures only work within the same sessionstate / scope chain. Annoying, yes.
I think you are making assumptions that don't hold. PSH is interpreted, so when a code block is created it just holds the source code. When it is later evaluated any variables it uses will be looked up in the normal PSH way: first in the current scope, and then in each outer scope until a variable with a matching name if found.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.