A solar-output pipe talks to a bureau feed, a store, a monitor, and the model; a new transform is tried beside the old one on the live stream; nobody is sure which code and which file set are in each place. What three pipeline checks should the tester combine?

A pipe that talks to a bureau feed, a store, a monitor, and the model, with a new transform beside the old one and fuzzy version identity, needs three checks together: system integration, a production comparison (including a named A/B of pipeline iterations), and a configuration-management review. A Chapter 6 A/B derivation, component-only testing, and skipping versions leave that trio incomplete.