F39-RT: Yes
Rationale
Reticulum applications use destination identities and the Link API for both co-resident and remote applications. Native shared-instance clients connect through Unix-domain sockets; the transport routes between local client interfaces or the configured serial network beneath the same application interface.
Assessment method
Official manual and version-pinned native local-interface source review
Source context
Reticulum 1.5.5 native shared-instance transport
Outstanding qualification
Explicit optional native profile selected for F39. Reticulum 1.5.5 LocalInterface.py creates AF_UNIX clients/listeners and registers local_client_interfaces; Transport.py handles their destination paths and forwarding. The shared instance and applications need a compatible configuration and permissions. The earlier standalone C08 witness remains separate. No local TCP, external broker, LXMF layer, zero-copy, runtime test or security-equivalence claim is introduced.
Public sources
- https://reticulum.network/manual/using.html
- https://github.com/markqvist/Reticulum/blob/1.5.5/RNS/Interfaces/LocalInterface.py
- https://github.com/markqvist/Reticulum/blob/1.5.5/RNS/Transport.py
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round694.html