MUP is just a protocol — it defines the format and communication between a MUP and its host, but it doesn't dictate how the host handles these things.
Conflict resolution depends on the host implementation. Different applications may need different strategies (queuing, locking, last-write-wins, etc.) — that's a host-level decision, not a protocol-level one.
Same for MUP-to-MUP communication. The protocol keeps each MUP isolated by design, but a host could absolutely build a coordination layer on top. In our PoC, the LLM acts as the orchestrator between MUPs, but that's just one approach.
The spec intentionally stays out of these decisions so it can work across different hosts and use cases.
MUP is just a protocol — it defines the format and communication between a MUP and its host, but it doesn't dictate how the host handles these things.
Conflict resolution depends on the host implementation. Different applications may need different strategies (queuing, locking, last-write-wins, etc.) — that's a host-level decision, not a protocol-level one.
Same for MUP-to-MUP communication. The protocol keeps each MUP isolated by design, but a host could absolutely build a coordination layer on top. In our PoC, the LLM acts as the orchestrator between MUPs, but that's just one approach.
The spec intentionally stays out of these decisions so it can work across different hosts and use cases.