This article mainly introduces configurable pipeline nodes. When developing pipelines for use‑cases, a newly‑developed use‑case may need to adapt to multiple cameras with different purposes, which brings about the issue of co‑existing configurations.Use‑case pruning enables activation of optically‑flow‑designed segments (nodes and target buffers) that implement shared logical interfaces without duplicating pipelines. However, implementations of these interfaces may conflict with one another. Therefore, attention must be paid to all cameras as well as pipeline design within each use‑case during usage.For example, suppose one camera requires AEC and AWB, while another camera does not. How should we design the system to satisfy both requirements within the same use‑case?As another example, how should we configure the system if one camera needs the IPE block whereas another camera does not use IPE at all?