>2) no, no, no - it's like saying "we don't need OOP if we don't need OOP" - great! then the whole discussion is mute.

I wasn't being that general, actually. :) What I was saying is that without knowing what this application actually does, it's impossible to say whether "moving" should be treated polymorphically or not.

>The whole idea is to "API" (black box if you prefer) these objects so that we don't need to know how they accomplish it - We say "move" and it moves per it's own interpretation of what that is

If that's the desired behavior, then fine. But I don't see how we can define that a priori.