> For the complete documentation index, see [llms.txt](https://www.isaacbowen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.isaacbowen.com/2025/04/03/natural-law.md). # natural law I remember: “STUDY NATURAL LAW” painted on someone’s roof in wisconsin, visible from the highway there are many natures how does this one work? — everything you can conceive of is supported by natural law until you can conceive of everything you observe *without distress*, maybe go easy on how much you believe in anything. or insist on anything? maybe that’s better. glowing eyes aren’t a villain trait. they’re functional. everything is. :) plenty of stuff outside of local nature too, but that’s not your ontological/epistemological jurisdiction. :) wait until you can build portals, then wait for visitors. experience only comes when you can host it. and *everything* is experience. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://www.isaacbowen.com/2025/04/03/natural-law.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.