G02-RT: Yes
Rationale
A configured regional transport node can learn a destination's changed serial attachment while suppressing unsolicited announcements toward an external access_point interface. A requester on that interface can obtain the updated path: Transport answers from its learned announcement, binds the response to the requesting interface and marks it PATH_RESPONSE to suppress ordinary rebroadcast. The node's destination/interface state and the interested requester's path can therefore change without disseminating the move to every participant.
Assessment method
Primary documentation and pinned source review; no runtime experiment
Source context
Reticulum 1.5.5 interface modes and path-response handling
Outstanding qualification
Bounded witness: retain destination identity/name and IFAC credentials; move between admitted serial attachments behind the same transport node; accept a fresh announcement there before the external requester retries discovery. Configure the requester-facing interface as access_point, keep it reachable and permit path responses. A fresh Link is allowed. This is native mode configuration, not a claim for default full-mode meshes or arbitrary inter-region moves. Stale caches, rate limits and recursive discovery can delay or broaden other cases. No global-capacity or uninterrupted-session result is inferred.
Public sources
- https://raw.githubusercontent.com/markqvist/Reticulum/1.5.5/RNS/Transport.py
- https://reticulum.network/manual/interfaces.html#interface-modes
- https://raw.githubusercontent.com/markqvist/Reticulum/1.5.5/RNS/Destination.py
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round559.html
- round559-sources.json