Why it matters
Source-attested integrity gives ForkMesh a concrete mechanism for fallback mirrors proving they match the state published by the source. Fallback serving is checked against integrity pins attested by the source of truth, so a mirror can prove it's handing you the same history the author published.
Code disappears from a network when one hosted account, one VM, or one storage path becomes the only way to reach it. In ForkMesh, source-attested integrity 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 source-attested integrity through the same split it uses across the product: nodes keep real Git mirrors, while the Worker coordinates signed HTTPS health, owner state pins, account lookup, and clone routing.
The behavior is intentionally narrow: Fallback serving is checked against integrity pins attested by the source of truth, so a mirror can prove it's handing you the same history the author published. The Worker helps find and route a live host, but it is not canonical Git storage.
Where it fits
Use source-attested integrity 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 Source-attested integrity keeps fallback mirrors proving they match the state published by the source connected to the repository, its signatures, and the nodes that serve it.