Mesh protocol

Mesh protocol envelopes are bounded, versioned and authenticated. They carry the minimum coordination data required to validate scope, sender, predecessor, membership epoch and payload digest.

Implementations should reject malformed, oversized, stale, unsigned or out-of-scope messages before application handling. Compatibility is explicit; unknown fields or versions must not silently expand authority.