F29-RT: No
Rationale
A Reticulum Resource advertisement is sent on an already selected Link to its peer. Destination hashes bind application/aspect naming to identity; request-handler paths are resolved at that destination. Resource hashes and part maps coordinate the chosen transfer, not network-wide supplier selection by content reference.
Assessment method
Primary specification and pinned-source assessment; no runtime experiment
Source context
Selected-composition documentary boundary; no added application service
Outstanding qualification
No for the selected Link profile. A custom request handler could implement a content service, but its callable and content-discovery convention would be additional application functionality. Resource advertisement is explicitly considered and is not interpreted as a network supplier announcement.
Public sources
- https://raw.githubusercontent.com/markqvist/Reticulum/1.5.5/RNS/Resource.py
- https://raw.githubusercontent.com/markqvist/Reticulum/1.5.5/RNS/Destination.py
- https://raw.githubusercontent.com/markqvist/Reticulum/1.5.5/RNS/Link.py
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round484.html
- round484-sources.json
- round484-plan.json