pipeline

A pipeline IS a specific kind of workflow — a linear chain of processing stages where data or state flows sequentially through each stage. Direction: specific→general.

Remove computation and a pipeline of processing steps cannot execute — the pipeline's operation requires computation to proceed.

Data pipeline is a specific kind of pipeline — a competent speaker would call a data pipeline 'a pipeline' (modified by data). This is a clean INSTANCE_OF per Law 9.

Nearest-kind filing (Law 11e) that the rejected signal-chain→audio-processing leap pointed at. Source accepted carve: 'a conceptual model in audio engineering that represents an audio signal's route as an ordered sequence of processing stages.' Target accepted carve: 'an ordered sequence of processing stages arranged so that the output of each stage becomes the input of the next, creating a directed chain of transformations' — requiring (1) ordered stages, (2) material/data flow between consecutive stages, (3) directed chain. A signal chain satisfies all three: the stages are ordered, each stage's audio output feeds the next, and the whole is a directed chain of signal transformations. Specific→general (Law 9): a signal chain is a pipeline whose material is audio. Pinned sense per Law 11d: the arrangement, not the operations inside it — which is precisely why the audio-processing target did not fit.