Anchorage API reference
    Preparing search index...

    Interface AgentThreadTopologyOptions

    How the agent topology honours idempotencyKey, or the typed opt-out.

    REQUIRED on createAgentThreadTopology for the same reason the run router's is: a topology that silently ignored a key would answer an exactly-once request with at-least-once behaviour, and the caller would have no way to find out. Writing 'none' is honest — it makes every keyed start refuse with IDEMPOTENT_START_UNSUPPORTED, and leaves unkeyed starts byte-identical.

    interface AgentThreadTopologyOptions {
        executionFence: ExecutionFenceWiring;
        remoteStepDispatch?: RemoteStepDispatchReader;
        remoteSteps?: RemoteStepContinuationReader;
        startIdempotency: StartIdempotencyWiring;
        workflowRemoteStepDispatch?: WorkflowRemoteStepDispatchReader;
    }
    Index

    Properties

    executionFence remoteStepDispatch? remoteSteps? startIdempotency workflowRemoteStepDispatch?

    Properties

    executionFence: ExecutionFenceWiring

    The deployment execution fence, so a REPLAY can re-assert a proof-only fence's binding to the run this key already made. Must be the fence over the SAME database the reservations live in; 'none' is the honest answer for a host with no fence.

    remoteStepDispatch?: RemoteStepDispatchReader
    remoteSteps?: RemoteStepContinuationReader
    startIdempotency: StartIdempotencyWiring
    workflowRemoteStepDispatch?: WorkflowRemoteStepDispatchReader

    Settings

    Member Visibility

    On This Page

    Properties