So you renamed "controllers" to "operations".
Out of the three terminologies (state, representation, flow), the third one is arguably the most tangled. I find it healthy to refactor it into reusable chunks (operations) and event-driven flow management.
The problem was, in my opinion, that operations should have not been put into controller units. It attracted more copy-paste solutions in my experience.
The original MVC designs and sample code all had views and controllers observing models through an Observer based event pattern.
The operations were the controller units. The events were not.
I'm going to have to agree with the parent here. Without example code to compare, how is this different than MVC? (or "MVCE")
http://emberjs.com/images/ember_mvc/embermvc.png
Operations are similar to controllers for sure. But where's routing or state? We don't have a full picture here.
After trying out that new meta-pattern, things get overly coupled, too many bi-directional relationships between state, views, models, and controllers/operations.
app.trigger 'boom'
Somehow, I'm just seeing the Observer pattern and the MVC pattern in the OPs post.