Most of our experimentation has presumed text message transfer. We should NOT presume that the data being transferred should be only text. We may allow transfer of any data type. This should be written to allow multiple data formats and data transports.
Consider this project: https://github.com/RecursiveMAS/RecursiveMAS.git I've made a fork here git@github.com:hartsock/RecursiveMAS.git to hold any experimental work we might do to extend the framework.
Which is accomplishing a similar multi-agent communications goal but is focused on Latent State Transfer. We want the agent-mesh to work well with broad use-cases like this as well.
Most of our experimentation has presumed text message transfer. We should NOT presume that the data being transferred should be only text. We may allow transfer of any data type. This should be written to allow multiple data formats and data transports.
Consider this project: https://github.com/RecursiveMAS/RecursiveMAS.git I've made a fork here git@github.com:hartsock/RecursiveMAS.git to hold any experimental work we might do to extend the framework.
Which is accomplishing a similar multi-agent communications goal but is focused on Latent State Transfer. We want the agent-mesh to work well with broad use-cases like this as well.