Why it matters
Public network map gives ForkMesh a concrete mechanism for making recently verified public-node availability and generalized mirror health visible without exposing private repositories or hidden device fields.
Code disappears from a network when one hosted account, one VM, or one storage path becomes the only way to reach it. In ForkMesh, public network map addresses that need at the feature level, keeping the behavior close to the repository instead of buried in a detached hosted layer.
How ForkMesh handles it
ForkMesh handles the public network map through the same split it uses across the product: nodes keep real Git mirrors, while the Worker coordinates signed HTTPS discovery, generalized health, presence, account lookup, and clone routing.
The behavior is intentionally narrow: freshness windows and active probes reduce stale routing decisions, but do not promise an instantaneous or infallible view. The Worker helps find and route a live host, but it is not canonical Git storage.
Where it fits
Use public network map when availability, clone routing, and preservation need to be handled by the mesh instead of by a single origin.
It pairs with the rest of Distributed hosting & preservation because Public network map keeps making live node availability and mirror health visible connected to the repository, its signatures, and the nodes that serve it.