Since these variables only exist at runtime, you'd need to create them programmatically by calling the API. To access them you could just use the expression Runstate.Execution.RunTimeVariables.<VariableName>.
Josh W. Certified TestStand Architect Formerly blue
It would be nice if the execution variables were not only runtime variables, so they would could be created normally (rather than programmatically) and browsed to normally.
Not only these RunTimeVariables are only creatable via the API, they are also terribly bad to see.
The same is valid for TemporaryGlobals which are even tedious to set and get (locals.whatever = TemporaryGlobals.GetValBool("Flag") ... hope I recalled the expression right, have no TS around here).
But worst of all is that the above are only mentioned somewhere deeeeep in the documentation. If you do not know they exist you are not likely to stumble over them.
I'm declining this idea due to lack of community support. Also, it's still unclear to me what is different about this idea from TemporaryGlobals