Under decision D1 a lane is a socket, and its properties come from the
locator metadata Zenoh was configured with (?rel=1;prio=0-2) — resolved
once, at startup, into this. A backend schedules lanes; it is never told what
a Zenoh priority is, which is what keeps Sdu traffic and Zenoh semantics
on opposite sides of this crate boundary.
Whether this lane promises ordered, loss-free delivery.
Per invariant I2 this is a claim about the medium, not a request. A
backend that cannot honour it must not be configured behind a lane that
asserts it: Zenoh will not notice the lie, because verify_sn accepts a
forward sequence gap silently — the failure mode is lost data, not a
fault.
Derived at configuration time from the lane’s declared priority range.
Rank 0 sorts first. The numbering happens to mirror Zenoh’s, where
Control is 0, but nothing here depends on that.