Modules
Railway Flow-Based Programming
The admission owner (FX-001): one process outside the replaceable stage subtree, holding its pipeline generation's admitted-work ledger.
The pipeline's answer before admission (FX-001), named by what the caller actually knows.
The library's own Application (T5 ruling, PASSON_FLOWEX_T5_RULING.md).
Abstraction to call the pipeline.
Consumes the pipeline data
Internal pipeline packet.
Pipeline process naming (T5 ruling).
The stage-side failure: a pipe callback raised, rescued into the packet's
error track. error keeps the original exception; pipe names the
callback that failed.
Defines macros for pipeline creating.
Defines functions to start and to stop a pipeline
The caller-side failure: the pipeline crashed, vanished, or missed its deadline.
Pushes data to pipeline
Pipes function is called here
Stage state: what to run, how, and where it sits in the line.
Pipeline supervisor — both the wrapper (admission owner + line) and the
line itself, always :rest_for_one.
Sync pipeline runner: one process, the line walked in a call. The state is
the prepared stage list (FX-007) — module init/1 already ran in the
starting caller, so the walker reuses prepared options and never
initializes per request.
Sync pipeline behaviour — one GenServer walks the pipe line.
Sync pipeline supervisor. Receives the prepared stage list (FX-007) —
module init/1 already ran in the starting caller — and bakes it into the
child spec, so a restart reuses the prepared options.