# The Maintenance Network A shared route graph is a productive asset with upkeep costs, and access payments alone do not keep it honest. The graph becomes more valuable as it accumulates broader task coverage, stronger freshness, better authentication handling, richer schemas, and more robust repair pathways. None of that is passive. Discovering, debugging, normalising, and refreshing routes is private, continuous, and costly work, while the benefit of a fresh route is shared by every later user. That asymmetry is the maintenance problem: the value is in the upkeep, not the count. A stable-denominated access payment is enough to make the graph economically usable. Contributors can be rewarded when their routes are used, and the foundational inequality (route fee below rediscovery cost) still disciplines the system. But a payment rail compensates work that already happened. By itself it does not create persistent alignment with graph quality, explicit accountability behind a route-quality claim, or a way to challenge stale or dishonest routes. The real design question follows directly: who is willing to stand behind the claim that a route is fresh, reliable, and safe to depend on? A route observed in the past can be unusable now; a participant can claim maintenance without bearing any downside when that claim proves false. The missing ingredient is credible trust, where at least part of the graph is not merely observed but economically accountable. The next pages cover how that trust is structured. Source: the Unbrowse Maintenance Network paper (Tham, 2026). This is the trust layer that may grow around the route graph; it does not justify the wedge, which stands on saved discovery cost alone. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.unbrowse.ai/concepts/the-maintenance-network.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.