Minimum claimable baseline
Required governance, firmware, identity, channel, administration, MQTT, privacy, and response controls.
Public review draft · v0.1
An independent, evidence-led baseline for organizations operating Meshtastic fleets. It defines minimum controls, acceptable evidence, stop conditions, and the limits of any conformance claim.
Independent publication. No certification or Meshtastic project endorsement.
Core conformance requires every applicable Core control to pass, no Core control to remain untested, and no stop condition to be present. A percentage score cannot override a stop condition.
Required governance, firmware, identity, channel, administration, MQTT, privacy, and response controls.
Additional lifecycle, provenance, monitoring, physical protection, and application-layer safeguards.
Control catalog
The canonical PDF contains every normative control, minimum evidence requirement, and source basis.
Fleet boundaries, accountable owners, and controlled exceptions.
Inventory, supported releases, staged updates, and firmware provenance.
Per-device identities, uniqueness checks, enrollment, response, and recovery.
Private channel keys, membership, sender limitations, and rotation.
PKC administration, managed mode, Bluetooth, serial, WiFi, and Ethernet.
TLS, credentials, ACLs, payload policy, downlink control, and monitoring.
Controlled network paths, operator endpoints, and unattended nodes.
Position precision, map reporting, metadata exposure, and approvals.
Configuration drift, identity changes, incident procedures, and recovery tests.
Core stop conditions
No compensating percentage or aggregate score can erase these conditions.
Evidence language
Every conclusion must retain its evidence state and tested boundary.
Directly present in scoped configuration, records, or logs.
Reproduced or corroborated beyond the originating assertion.
Reasoned from observations with the logic and limits stated.
A working premise that remains unestablished.
Evidence was unavailable, inaccessible, or outside scope.
Public review
The v0.1 review window closes October 1, 2026. Identify the control ID, disputed behavior, deployment context, authoritative evidence, and proposed replacement language.
Submit baseline feedbackMeshProof Forge will recheck upstream support, stable releases, advisories, and trademark guidance at least monthly while v0.1 is current.
Canonical files
The hashes below identify the current public review files published from this page.
c9dd98ed769994f4c93a3577f5d62af297cf35143ed00b90adbe8c6fdf3640baDownload canonical PDF ↓7ceb711be91b1acbf91a0ff03978bc6ee1cb380d08f2d2f2ccaca67cef002561Download sample assessment ↓30bdb87c1b774fad8b27cab97cbac0e1b425e1fbe5b1790a5a85d7f0163460dcDownload pilot scope ↓Copyright 2026 Red Asgard. All rights reserved. Short excerpts may be quoted with attribution and a link to this canonical page. Redistribution, translation, modification, or publication of derivative editions requires written permission. Do not represent modified copies as MeshProof publications.