They would live as independent entities within a notebook just like regular notes do. But it means that these 'project-notes' would not be surrounded by relevant rich context the way the current in-note tasks are. This would effectively turn the in-note tasks (currently the only type of tasks) into sub-tasks. You can manage it in the Tasks view just like you manage all your existing tasks today. If you turn it into a 'project-note', it means it's just like a regular Evernote note except you can also mark it complete and put a due date on it.

You could do this for some of your note, all of your notes, or none of your notes. We're asking because it is probably way faster for us to give you the ability to turn the note itself into a 'task-note' or 'project-note'. How important is it for you to have rich context for both the parent tasks and the sub-tasks that are associated with them? Could you live with having rich context only for the sub-tasks? Now start thinking about how you would want sub-tasks (incredibly highly requested feature by our users) to work. Let's call that capability 'rich context for tasks.' Here are two videos we've created that give specific examples of this and why we think it's powerful:

You can take advantage of all the power of the Evernote note editor to surround your tasks with information that will help you get them done. One of the big advantages of the fact that tasks are embedded in notes is that you have context for them. We are keenly aware of the limitation to, and we are actively working on this problem.

Evernote task