'Push what's changed' is not a typical description of 'lazy' evaluation. As was said in a sibling comment, lazy is more of a demand-driven evaluation. However, I think you are more likely leaning into describing reactive programming paradigms. the description in parent is not exactly describing reactive, but it is certainly in the 'wheelhouse' of reactive programming. Typically, node based compositing is definitely reactive, and is most often lazy as I discuss in a sibling post.