Not know for sure, I'd rather start with less code and only add more as we find we need it later.

When you get down to it, these "models" feel more like models in Rails: they're not business logic but proxies to records in a database. I'd rather have the syntactic sugar in another layer of abstraction.

But, as you say Chris, given all that, I'd just as soon delay the decision and remove the code entirely for now.