F05-MT: Yes
Rationale
The selected F16 headless KNOWN_ONLY/STRICT witness includes locally authorized User records, confirmed full peer keys and an ignore policy, not merely retained destination keys. Router rejects unknown senders before first-contact learning and applies the retained cryptographic checks to admitted records. Keeping that configured admission context while delivery/radio activity stops allows later messages from the same authorized peer after a compatible authorized reattachment. No transport-session object is required by F05. The previous No considered per-message key derivation but omitted the already selected admission policy.
Assessment method
Selected-profile consistency correction; no runtime execution
Source context
Pinned Router and NodeDB plus the already selected F16 policy witness
Outstanding qualification
Use the explicit F16 witness, not the separate C04/C08 CLIENT/ALL probe configuration or a database populated by arbitrary learned peers. Preserve authorized records, full-key bindings and ignore policy; peers must still share compatible radio/channel settings. No automatic channel migration, cross-medium bridging, replay suppression or new firmware/radio test is claimed. Storage and cold-start controls remain those already required by the selected witness. Packet-oriented operation does not by itself establish continuity: the retained admission decision is essential.
Public sources
- https://github.com/meshtastic/firmware/blob/8e6a88d06f44cad26f1e8d7cd402939ccacb9b4c/src/mesh/Router.cpp
- https://github.com/meshtastic/firmware/blob/8e6a88d06f44cad26f1e8d7cd402939ccacb9b4c/src/mesh/NodeDB.cpp
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round122-sources.json
- round290-sources.json