vigiles API reference
    Preparing search index...

    Interface RailwayStep

    One step on a railway: dispatch a flat subagent (the "activity").

    interface RailwayStep {
        _step: "delegate";
        agent: string;
        needs?: Readonly<Record<string, OutputFieldType>>;
        task?: string;
    }
    Index

    Properties

    _step agent needs? task?

    Properties

    Readonly_step

    _step: "delegate"
    agent: string

    The subagent to dispatch — resolved against compiled agent names.

    needs?: Readonly<Record<string, OutputFieldType>>

    Optional input contract the step reads from its predecessor's result().ok. When present, the whole-harness registry (generate-harness) emits a per-edge Handoff<> assertion so a CROSS-FILE handoff mismatch (a missing field or wrong type vs the prior step's ok) is a tsc error naming the field. Absent needs = no handoff check (today's behavior, the string-path backstop). Built by needs(...), the same builder a typed pipeStep uses.

    task?: string

    Optional task hint passed to the worker.

    Settings

    Member Visibility

    On This Page

    Properties