I'm not saying MVC is the only way. I've not even mentioned MVC. What I gather though is that when you hear someone mention frameworks you assume they are referring to the railish frameworks of recent. A framework to me is a set of libraries and a structure to better layout and facilitate the development of your application.
It also doesn't have to be a premade/3rd party one as you've demonstrated by essentially creating your own framework and just calling it by a different name(collection of libraries).
A recipe for disaster in my opinion would be a large project with no code structure/layout guidelines.
The term framework is almost exclusively used for object oriented designs. That's what I was arguing against.
Of course one should make, use and keep improving his own libraries.
And there's nothing wrong in using other people code either. Provided that it is built in a modular standalone fashion and so it can be easily included / replaced / updated / removed without breaking things.
It also doesn't have to be a premade/3rd party one as you've demonstrated by essentially creating your own framework and just calling it by a different name(collection of libraries).
A recipe for disaster in my opinion would be a large project with no code structure/layout guidelines.