Anchorage API reference
    Preparing search index...

    Type Alias ExecutionFenceWiring

    ExecutionFenceWiring: ExecutionFenceStore | "none"

    How a surface is wired to the fence: a store, or the typed opt-out.

    Written as a union with no undefined so every option type carrying it can be REQUIRED. That is the whole forcing function: a fence option a host may omit is one a host will omit, and a partially wired deployment is worse than an unwired one — an unfenced schedule tick claims a due fire through the CAS (which advances nextFireAt) and the fenced runtime then refuses the start, so the fire is consumed and never runs. Making the caller WRITE 'none' turns that split brain into a decision someone made rather than one they missed, and 'none' stays honest for the callers that genuinely have no database to fence against (in-memory tests, adapters).