# The Maintenance Problem Once a shared route graph carries meaningful traffic, the hard question is no longer discovery but maintenance. The first product claim, that shared lookup beats browser rediscovery on cost, latency, and reliability, is enough to justify the wedge and needs no token or economy to be true. The Maintenance Network paper is explicit that the wedge already works without a native asset. The second question only arrives later: once many agents depend on the graph, how is route quality coordinated over time? That second question is a coordination problem, not just an engineering one. It involves participants who discover routes, normalise them, keep them fresh, challenge stale or dishonest claims, and accept some accountability for quality. Simple access payments do not solve this, because paying to call a route says nothing about whether the route is still good. The paper's framing is deliberately quiet here: the interesting layer is a maintenance network with accountable participants and challenge mechanisms, not a louder token story. Trust and accountability are treated next, at that same restrained altitude. --- # 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-problem.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.