Here are some message types that Monty could conceivably employ, along with some implementation notes. Note that this is all pretty speculative and I’m probably missing some clues about Monty, so any help would be appreciated.
- :grow - This message might ask its recipient(s) to set up more connectivity and/or modules, with specified settings, tags, etc.
- :mcp - This message tells its recipient(s) (e.g., LLMs) about the semantics of given models. This would be encoded in Model Context Protocol (MCP).
- :move - This is the canonical motor control message which LMs already send to the motor system(s).
- :sync - This message would be sent out to all modules to help them keep their clocks in sync. This could be based on Network Time Protocol (NTP).
- :tell - This message asks its recipient(s) to provide specific information about their internal state. This could be based on GraphQL.
- :vote - This is the canonical message which LMs already exchange. It basically says “This is my model of Foo; deal…”.
- :yell - This message claims a high level of priority.
(ducks)