Create TASKS.md

OS/TASKS.md

@@ -0,0 +1,2 @@
+- [ ] Decide: better queue?
+So, Michael suggested we simply watch and filter the `dmesg` stream (I think that's what it's called?), so I suppose we could have a script like `/01/core/kernel_watch.py` that puts things into the queue? Honestly knowing we could get it all from one place like that— maybe this should be simpler. **Is the queue folder necessary?** How about we just expect the computer to send {"role": "computer"} messages to a POST endpoint at "/queue" or maybe "/inturrupt" or maybe "/" but with POST? When it gets those it puts them in the redis queue, which is checked frequently, so it's handled immediatly. So then yeah, maybe we do have redis there, then instead of looking at that folder, we check the redis queue. This feels better tbh. Then we could have `/i` which other interpreter's hit. That behaves more like the OpenAI streaming endpoint (i think this is important for users to see the exchange happening). You could imagine some kind of handshake btw— another interpreter → /i → the sender is unrecognized → computer message is sent to / which tells the user to have the interpreter send a specific code → the user tells the sending interpreter to use that specific code → the sender is recognized and added to friends-list (computer.inet.friends()) → now they can hit eachother's i endpoints freely with `computer.inet.friend(id).message("hey")`. When transfering skills that require OS control, the sender can replace those skills with that command, with one input "natural language query" (?) preceeded by the skill function name or something like that. Basically so if you ask it to do something you set up as a skill, it actually asks your computer to do it. If you ask your computer to do it directly, it's more direct.