G03-CJ: Yes
Rationale
In the selected cjdns route-server composition, SubnodePathfinder sends a getRoute query containing source and target to its configured server, then passes the returned route to the forwarding core. Ordinary clients and transit switches do not require their own complete copies of the server graph or all final participant identities.
Assessment method
Primary specification and pinned code review; no runtime experiment
Source context
Selected discovery and pathfinder mechanisms
Outstanding qualification
The numeric target, reachable configured server and local peer connectivity remain prerequisites. Servers may hold broad or complete graphs; G03 does not prohibit concentration at a particular role. This is the selected route-server design, not a legacy-DHT claim, and does not establish partitioned server storage, server independence, bounded lookup cost or global scale.
Public sources
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round496.html
- round496-sources.json