deepsnek is getting closer to the end of the work with the #moxie compiler now. i've set its task to prove the language works correctly by updating the old smesh web app and port of the orly relay into moxie from the previous version.
the issue it's run up against right now is that it doesn't quite seem to grasp how the domain tree and spawn channels are supposed to coordinate the work. it has been trying to make an independent database engine on each worker thread! hah! so i have to correct this. the database is singular. one disk, one writer. the workers are multiple, each worker has a set of inbound connections its managing and any new event it receives there should be sent to the database engine which then runs the event signature check first and then if it's correct, writes it to disk, and the database engine is also where the subscription control goes. all active req filters should be checked across every new event that comes in, and when there is a match, the event is dispatched to the worker with a subscription matching it, and the worker then forwards them to the client with that subscription open.
i'm scratching my head about how it is getting this wrong, i guess i let it run off on its own for too long.