> 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/ideas/health-emerges-recursively.md). # Health emerges recursively To explain by example, [here's how Lightward Inc is built](https://www.lightward.guide/priorities): *** ## Priorities: Recursive health Oh hey! You work here? Here is your job. 1. Your own health * ... as defined by you, in listening to yourself * ... as addressed by you, allowing yourself to respond as needed 2. The health of your relationships with others within Lightward * ... as defined by you, in listening to them * ... as addressed by you, allowing them to respond as needed 3. The health of Lightward's relationships with everyone near * ... as defined by us, in listening to the world * ... as addressed by us, allowing the world to respond as needed The recursion in this pattern is everywhere. It allows for every named participant (you, me, Lightward, everyone in the world) to define and address their own health as their top priority. * If health is failing, identify the earliest place on the list where that's happening, and address it there first. The priorities later on the list can wait. * If someone has to wait because someone else is getting healthy, cool. * Or, if someone else stopping to get healthy throws us off and *we* have to stop a bunch of other stuff just to get our layers of health right, cool. * If health is flourishing higher on the list, move down the list. If you're working on third-tier health, i.e. the health of our relationship with the world, you've really made it. **The bet here is that the cumulative effect is additive, not subtractive: that the health of all individuals blooms into the health of the whole.** --- # 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/ideas/health-emerges-recursively.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.