Yes. What about things which shouldn't be in the model but might be necessary when invoking an editing page? Authorising the current user, validation of the supplied input data, routing different scenarios through to different views, etc.. Is that all to be done in the model?

Very good to hear that you're planning on allowing more dynamic routing! cookie::get is only a helper, it can call Dingo::cookie if you really want it to. Without it, the API just seems unbalanced.