The following diagram illustrates the overall architecture of the MOSH library.

The Element Manager is the hardware-to-MOSH interface. It reads raw hardware data, and separates it into properties used by other MOSH elements. This separation allows an elements properties to reflect their intended use more clearly, and enables different properties from the same device to be routed independently. For example:

• A basic switch's hardware state (0 or 1) is read by the Element Manager, and provides it to other MOSH elements as its logical state (e.g., On or Off).

• A GPS module may provide multiple properties—location and time—that can be assigned to different Virtual Wires.

The Element Manager also maintains a list of element properties to be the used by the Virtual Wire Manager.

The Virtual Wire Manager is responsible for routing messages between elements based on their assigned virtual wire IDs. It acts as a logical patch panel, allowing input elements (like buttons, sensors, or timers) to trigger actions on output elements (like LEDs, relays, or motors) without direct coupling.

By abstracting the connection layer, the Virtual Wire Manager enables modular, transport-agnostic automation across distributed nodes. It ensures that status or property change messages are delivered in real time to all elements subscribed to a given wire, regardless of their physical location or transport layer.

Virtual wires form the backbone of decentralized automation in MOSH.

The Message Framer is responsible for a variety of MOSH functions. Some of these functions include:

• The final construction of MOSH Messages
• Accepting message requests from the Virtual-Wire Manager
• Accepting/Sending messages to/from the Transport Manager