sure, I was already thinking about that. but it isn’t a solution for the fact that this process is painfully manual.
ideally you would want to use sets for that and not collections. the problem is that sets display all objects of the same type and the idea of sub-collections doesn’t seem to exist in Anytype. this means that if you want to have a ‘projects’ dedicated set, everything, your project children-sets and the objects inside them will all show.
@Axis solved it by manually adding an index relation and a secondary index relation for every project’s sub-object 
just the idea of it makes me tired.
I want Anytype to do it all for me. I want to configure my format once by setting a parent-set called ‘projects’ that can ONLY house children-set (each set is a project). so that when I open my ‘projects’ parent-collection and press add new object, a new child-set would be added. this child-set should have a template that I created that carries the recipe of views I designed with their filters and relations already configured. the new child-set (new project set) would have a ‘notes’ view and a ‘tasks’ for instance. then if I open the child-set (that’s project 1) and go on to the notes view tab and press add new, a new object in the form of a note will be added and shown only in this set because in its template the relation to the project 1 set and the index that this object is a note (and not a task), will be baked in the template.
the aim is to be able to sort objects based on their parent-objects and simply be able to navigate to the location where you want to plant a new object, and do it without having to think so much or preconfigure it. because when you wish to log a task or quickly write down an idea, you want to write it off your mind and on to the page as soon as possible.