On this podcast http://5by5.tv/rubyonrails/181 the guest, Brian Cardarella, mentioned "pushing all the data through a single choke point". He was talking about a proxy (which I think maybe Ember Data does).
I feel like the Flux framework also has a similar idea... the single choke point with (in their case also with a queue that ensures things happen in a reasonable (literally 'able to be reasoned about') way)
From http://facebook.github.io/flux/docs/overview.html
"Flux eschews MVC in favor of a unidirectional data flow. When a user interacts with a React view, the view propagates an action through a central dispatcher, to the various stores that hold the application's data and business logic, which updates all of the views that are affected."
Ruby has an interesting method called "tap" that allows you to tap into the middle of a chained set of enumerable operations to, for example, print out stuff as it is at that point. I feel like being able to tap into serial communication (by pushing all the data through a single, inspectable, choke point) has pretty big implications for highly complex interactions (where changes can come from notifications, external data being loaded, and user interactions)
In this blog post, the guy mentions the name "bottleneck method" http://indiestack.com/2015/01/same-tests-different-class/ Seems like a similar idea and interesting name for it.