No, I think both mine and @lorenzo's thinking is that the `ORM\Table` table class will replace the Model class. It will contain methods like find(), save(), updateAll, delete() and deleteAll(). They are also where Behaviors and validation sets will be defined. The entity classes provide record level logic, computed fields and make interacting with data simpler.

I don't think the Model class has a purpose after the other two classes are complete. Our current goal is to provide a rock solid SQL backed ORM. We hope to extract a set of interfaces that make using other datastores like mongodb and elasticsearch easy. Unfortunately creating a single abstraction on top of both relational and non-relational datastores usually results in the worst of both worlds. My longer term goal is to replace the various `Table` typehints with a `RepositoryInterface`, and possibly a QueryInterface. Both these interfaces should be able to afford implementations backed by non-relational stores.