> For the complete documentation index, see [llms.txt](https://switch-protocol-1.gitbook.io/switch-protocol-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://switch-protocol-1.gitbook.io/switch-protocol-docs/09-conclusion.md). # 9. Conclusion Two design decisions carry this protocol, and both are subtractive. The first is that **rewards are denominated in assets the protocol does not issue.** This forecloses the reflexive loop described in §2.1. Switch cannot inflate its way to a headline yield, because it cannot print what it distributes. Distribution volume falls when trading falls — but the mechanism does not depend on new capital to make prior distributions good, because they were never denominated in a claim on the protocol. The second is that **selection is arithmetic and settlement is a push.** There is no manager to trust, no mandate to renegotiate, no key to compromise, and no claim transaction to remember. What the protocol will do in any given hour is a published function of public inputs; what it did in every past hour can be recomputed and checked by anyone. Neither decision is free. Immutability means a discovered flaw cannot be patched. A deterministic momentum rule will buy local tops, and will do so visibly, on the record, in full public view. Volume-linked distribution means quiet weeks pay little. These costs are accepted deliberately, and they are stated here rather than discovered later — because the entire proposition is that the protocol does what it says, and a document that oversold it would be the first counterexample. Most protocols pay you in their own token, and ask you to claim it. Switch pays in assets it did not create, and delivers them while you do nothing. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://switch-protocol-1.gitbook.io/switch-protocol-docs/09-conclusion.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.