Table of Contents

Architecture Map

Purpose

This page explains how the major MOSH subsystems relate to one another.

Layered View

Layer Responsibility
MOSH smart-home logic, node behavior, elements, virtual wires
IMC carrier abstraction and message boundary
MTRP routing, forwarding, path selection, transport-neutral packet handling
Transport physical or link-layer communication such as ESP-NOW or NRF24
Hardware boards, radios, peripherals, and device-specific capabilities

Relationship Summary

MOSH describes what the node wants to do.

IMC describes how MOSH hands that intent to a communication carrier.

MTRP describes how packets are routed, forwarded, and delivered across one or more transports.

The transport layer describes how bytes move over a specific link.

Message Flow

A typical message path looks like this:

  1. MOSH creates or requests an action
  2. IMC hands that action to a carrier
  3. the carrier uses MTRP to route or deliver the message
  4. MTRP selects a path and uses a transport
  5. the receiving side processes the message and returns it upward

Important Separation

MOSH and MTRP solve different problems.

IMC exists so those layers can evolve without being tightly coupled.

Design Benefit

This structure allows:

Where To Go Next