Design pattern/guidelines to architecture Rust code

Hello everyone !

On my project, a Minecraft bot, I am stuck on how to architecture the different parts.

What resources inspires you on how to architecture your code correctly, as the type system and borrow checker prevent some patterns you would use in other languages (like python or js)?

How do you makes different parts of your code communicate without using Arx<Mutex<T>> everywhere?

As an example of what I have done : I have a bunch of systems (structs) that only receive data from the network and update themselves. However, one of the first thing to do when logged in is to send back a teleportation confirmation with an id. Who should send it ? The data storing part, a dedicated system, which my duplicate data from the data storing part ?