A framework is a collection of libraries (which can certainly have ways of handling input, scenes, maps, and so on). However, game developers need to connect all the tools and components to create that magical black box called a game engine.
A game engine is a framework that allows you to create a game by adding and altering values for scenes, maps, scripts, objects, and so on. So, you initialise the engine, add and set a scene, add an object to that scene, call the magical .run()
command, and 'it just works' (the game loops, input events occur, it renders your scene, map, and object to the screen — and you, the game developer, don't have to know how any of that works).
So, the answer to whether your project is a framework, a game engine, or just a game, depends on how you plan on releasing your project:
- Are you releasing a collection of libraries such as a menu system, a dungeon generator, and a scene and map handler (with no magical .run() command)?
- Or, are you releasing a 'black box', where your designer only needs to create and add content, and where a magical .run() command handles everything?
- Or, are you releasing a game, which has a game engine, and which, excluding mods and source code salvaging, is not designed to be the skeleton for new games?
With that said, terms are often open to interpretation. So don't take anything I wrote as fact. Ultimately, what you call your project is up to you. Hell, one might expect your curiosity is actually procrastination. And, if that is the case: forget the semantics, and get to work!