I updated the class-list, and also put a possible file hierarchy there.
Let’s try and come up with as much desired API as we can, and build top down? It may be impossible to fully predict what we want, but we already do have an idea from Famous oh-three and Engine.
I think what we should do is all work together to finish our ideal design spec over at infamous/requirements and then continue building our prototypes based on that spec (but not necessarily strictly following the spec), then after that we can decide on our merge plan.
The reason we don’t have to stricly follow the spec is because in making our prototypes we might discover we want to do something differently, and we can present our reasoning for that when we are ready to discuss our merge plan.