Read the fence a surface was wired with, resolving the typed opt-out.
ONE function rather than a fence ? await fence.read() : OPEN at every gate,
because those are the places a mistake is invisible: an unfenced surface and
an open one behave identically until the day an operator closes the fence, so
a call site that got the ternary subtly wrong would pass every test written
against an open deployment. Every gate resolving absence through here means
there is exactly one definition of what "no fence" does.
undefined is admitted alongside 'none' for the surfaces whose fence
arrives through an object the caller may not have populated (an
InitResult.executionFence on an unfenced host); it reads as open for the
same reason 'none' does, and never as a silent default a host can reach by
forgetting — the option types that feed this are required.
Read the fence a surface was wired with, resolving the typed opt-out.
ONE function rather than a
fence ? await fence.read() : OPENat every gate, because those are the places a mistake is invisible: an unfenced surface and an open one behave identically until the day an operator closes the fence, so a call site that got the ternary subtly wrong would pass every test written against an open deployment. Every gate resolving absence through here means there is exactly one definition of what "no fence" does.undefinedis admitted alongside'none'for the surfaces whose fence arrives through an object the caller may not have populated (anInitResult.executionFenceon an unfenced host); it reads as open for the same reason'none'does, and never as a silent default a host can reach by forgetting — the option types that feed this are required.