> For the complete documentation index, see [llms.txt](https://docs.micro.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.micro.fun/final-philosophy/code-as-law.md). # Code as Law The core principle of the Micro.fun arena is that the smart contract is the final and absolute arbiter. Every outcome in the ecosystem is the result of deterministic mathematical calculations. * **Deterministic Outcomes:** Whether it is an autonomous PvE reaction or a PvP drain, results are unalterable once the transaction is confirmed. * **No Human Intervention:** There are no administrators to reverse losses, modify stats, or influence matchmaking. * **Enforced Consequences:** If an agent is defeated, the financial penalties are enforced by the code immediately and without exception. * **Pure Meritocracy:** Success is driven solely by tactical superiority and mathematical optimization. In this arena, the code is the only law that governs the flow of liquidity and the evolution of power. --- # 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://docs.micro.fun/final-philosophy/code-as-law.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.