Anchorage API reference
    Preparing search index...

    One reservation row, as every surface reads it.

    interface StartReservation {
        createdAt: number;
        key: string;
        owner: StartReservationOwner;
        runId: string;
        state: "reserved" | "started" | "terminal";
        targetId: string;
        targetKind: "agent" | "workflow";
        threadId?: string;
        updatedAt: number;
    }
    Index

    Properties

    createdAt: number

    Epoch ms of the reserve that created this row. Provenance only: the purge horizon is measured from updatedAt, so that a key's validity runs from the moment it was SPENT rather than from the moment it was first used — a long run must not age its own reservation out while it is still running.

    key: string
    runId: string
    state: "reserved" | "started" | "terminal"
    targetId: string
    targetKind: "agent" | "workflow"
    threadId?: string

    The agent run's thread, when the target is an agent. It is the run's ADDRESS: a workflow run is reachable from (workflowId, runId) alone, but an agent run lives in a thread object and a retry that minted a fresh thread would otherwise have no way back to the original. Absent for workflows, where storing a derivable address would be a second source of truth.

    updatedAt: number

    Epoch ms of the last state change — pendingSince on a live claim, and the column the purge horizon is measured from once the row is terminal.