# Accountable Bonding and Where FDRY Fits Optional bonding, if it exists at all, purchases credibility and accountability, never ranking or distribution. ## Bonding is a warranty, not an ad slot If bonding is framed as a way to buy visibility or rank, the graph collapses into pay-for-placement and loses legitimacy. The correct principle is narrow: a maintainer who posts a bond is not paying to be seen. They are making an economically accountable claim that a route works, is maintained, meets the standards of the trust tier it serves, and that there are consequences if that claim is false. That is closer to a performance bond than to payment or advertising. ## Challenge mechanisms make claims falsifiable Bonding only means something if claims can be tested and false ones carry consequences. A challenger who observes that a route is stale, broken, or misrepresented can dispute it. If the challenge succeeds, the graph updates the route's trust state and the accountable maintainer can be penalised. If it fails, frivolous disputes are not free. Maintainers make accountable claims, challengers test them, the graph updates trust on evidence. The point is not token theater. The point is economic falsifiability. ## Usage settlement and the security asset are different problems Route usage and route maintenance are distinct coordination problems and need not share an asset. Ordinary route access is best served by stable-denominated settlement, because routine consumption wants transactional predictability, not pricing variance. The maintenance problem is different: a higher-trust tier requires participants to bear downside for false claims, which is collateralised accountability, not payment for use. A native asset, if introduced at all, is more naturally assigned to that security function than to routine usage. ## Where FDRY fits FDRY does not justify the wedge. The route graph is already justified by saved discovery cost. FDRY appears only at the layer where the graph needs an optional coordination mechanism for accountable participation in higher-trust maintenance and dispute resolution. That is a much narrower and more defensible role than a universal payment token, a governance wrapper, a ranking token, or a symbolic ownership claim. The strongest reading is deliberately modest: FDRY is useful only if and when the graph matures to the point that optional bonding, challengeability, and accountable high-trust maintenance become necessary. Nothing in the wedge depends on forcing that conclusion early. ## Practical sequencing 1. **Phase 1, prove the wedge.** Shared route lookup beats browser rediscovery, route economics are real, the graph saves time and cost with no token dependence. 2. **Phase 2, strengthen maintenance.** Route health and freshness, better attribution, challengeability, trusted and premium route classes. 3. **Phase 3, optional accountable bonding, only if needed.** Only if higher-trust maintenance becomes important enough to justify it, and only if it improves accountability without corrupting ranking or UX. This sequencing keeps the product honest and prevents optional coordination mechanisms from becoming premature narrative burdens. A fuller version of the Unbrowse Maintenance Network paper is being prepared for public release; this page tracks its current public form. For the token's neutral disclosure, see [FDRY Token Disclosure](/reference/fdry.md). Source: the Unbrowse Maintenance Network paper (Tham, 2026). It extends, and does not replace, the core whitepaper. --- # 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/accountable-bonding.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.