Strict documentation policy: every important claim is either verified by repository contents and/or commands executed in this run, explicitly marked NOT VERIFIED, or removed.

Verified by test execution (Windows / MSVC / CMake, POSIX port):

• CMake configure/build succeeded for -DUMESH_PORT=posix -DUMESH_BUILD_TESTS=ON
• ctest ran 13 tests and reported 100% pass (13/13)
  Evidence: VERIFICATION.md

CI (configuration only):

• GitHub Actions workflow exists for Ubuntu + Windows POSIX builds: .github/workflows/ci.yml
  NOT VERIFIED: whether CI is currently passing on GitHub.

µMesh is a C99 library that implements a small mesh-style protocol on top of a “raw 802.11 frame” PHY abstraction with separate modules for:

• PHY abstraction: src/phy/ (+ ESP32 and POSIX ports in port/)
• MAC: src/mac/ (send path includes CSMA/CA/backoff + ACK/retry logic)
• Network: src/net/ (discovery + routing modes)
• Security: src/sec/ (AES-128-CTR + HMAC-SHA256 truncated MIC + replay window)
• Optional power-management module: src/power/ (compile-time gated)

See:

• VERIFICATION.md (commands run, results, and what was NOT run)
• docs/DIAGRAMS.md (Mermaid diagrams derived from the code paths)
• SECURITY.md (threat model + limitations; no “strong security” claims without proof)

Package / release version currently implemented in code: 1.5.0 (docs/IMPLEMENTATION.md mirrors the versioned package metadata). v1.4.0 is historical and remains unchanged.

Release tag prepared in this release: v1.5.0 This tag is separate from the wire protocol version and from compatibility wrappers.

Wire protocol version: UMESH_WIRE_VERSION in include/umesh.h This field is independent from the package/release tag.

NOT VERIFIED: Git tags / GitHub releases in this run beyond local git inspection.

The public header is include/umesh.h. For configuration fields and defaults, see docs/API_REFERENCE.md (defaults are derived from code in src/umesh.c and constants in src/common/defs.h).

This repository (and this run) does not provide measured evidence for radio range, throughput, latency, or current consumption. Any such numbers must be backed by reproducible measurement artifacts (hardware, antenna, channel, TX power, environment) and linked from documentation.

• docs/COOKBOOK.md
• docs/API_REFERENCE.md
• docs/KNOWN_LIMITATIONS.md
• CONTRIBUTING.md
• SUPPORT.md
• docs/SECURITY_LAYER.md
• docs/PHYSICAL_LAYER.md
• docs/MAC_LAYER.md
• docs/NETWORK_LAYER.md
• docs/POWER_MANAGEMENT.md
• docs/KNOWN_ISSUES.md

MIT (see LICENSE).