These are all excellent suggestions and constitute a great framework for
enhancing or extending MVC and Morphic.

I'd just like to add that for the purposes of internationalization, you want
to separate all literals into resources (a la Mac resource forks or a la more
mainstream resource files.)

You can do this internationalization either:
 through a single resouce dictionary which associates
   a part by label with a dictionary which associates
     associating a language with a lileral entry
 or with a simpler dictionary but at the cost of a proliferation of resource
files or forks.

You might also want to make use of some global for keeping track of the
current language of operation.

I've found that these things are hard to retrofit (you always forget something
so QA is a time wasting expensive pain,) so its much better if your start your
design with them in place. Then its a lot easier to support a multitude of
languages, writing scripts, character sets etc.

-Charles-A.