I think the point is, there is no explicit state, order, history etc in Reticulum only destinations who announce that they are there and nodes who know to which node they have to send a data package r...
That sounds sensible and underappreciated indeed.
2WAY is concerned with what happens once data reaches the node and multiple parties can affect the same state. Shared state needs rules that are explicit and applied the same way everywhere, otherwise different nodes will reach different conclusions over time. In 2WAY those rules are enforced by the system itself rather than reconstructed by applications. It sounds like Reticulum can move data very well, but does not aim to define or enforce shared history, which is the problem 2WAY is built to solve.
2WAY is concerned with what happens once data reaches the node and multiple parties can affect the same state. Shared state needs rules that are explicit and applied the same way everywhere, otherwise different nodes will reach different conclusions over time. In 2WAY those rules are enforced by the system itself rather than reconstructed by applications. It sounds like Reticulum can move data very well, but does not aim to define or enforce shared history, which is the problem 2WAY is built to solve.