I'm pretty sure that ember had an internal object called Ember.State at one point and another called Ember.StateManager to (naturally) manage the relationships between states. This was a few years back so I can't say what's happened internally since then, but as far as I remember the router was intended to basically encapsulate the logic of an FSM.
Yep, you are right. There was Ember.State and Ember.StateManager, but it was extracted from the final v1.0.0. Instead of having one universal State Manager, router, views, etc got they own.
After spending 15 minutes in the source code, it is ready to use... for example, it is brilliant to manage states in a component tree, where the original router would overkill.
