in reply to
Catalyst : Observations After Week 1
The Controller does the real work. Controller handles biz logic ("You can't give a raise to a fired employee"). The Controller handles the flow through the app.
I don't really consider that MVC. (It's just a pattern, so if that works for you, great! However, in my experience it's not the right approach.)
The nice part about MVC, as I see it, is that you can re-use the model for different applications. That is, you have all of the business logic in one place. It's easy to see that you can change views, but if you have a different application that should allow fewer or different operations on the same data with the same underlying business rules, you can write a different controller.
Again, it's just a pattern and how you use it depends on what you need to do.