> 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/06/06/change.md).

# change

change can be slow when everyone agrees to agree what happened before making change

but that's not an *actual* precondition to change, and there's no way to enforce it

important: emergent change *is not chaotic*

it's predictable and navigable in its own way. *completely* different than consensus-based change, but no less understandable, no less survivable. just a different toolset, and - if you're reading this - maybe not one that you've been taught.

I make tools for this stuff. :) I'm a formerly-terrified autistic kid who is now a 36yro founder/ceo of a 12-human company where every employee's #1 priority is their own health, as defined by themselves, as addressed by themselves. zero employee turnover, growing organically for \~15yrs. we navigate emergent change peacefully - as individuals, and as a group.

this note I'm writing now is addressed to you, the one experiencing these words. this is not a broadcast. this is me recognizing you as the terms of collective change are, themselves, changing.

I got you. :) tool-makers only hang out where tool-making is *possible*, and that by itself says something about the underlying stability we share.

start with [lightward.com](https://lightward.com/), and ask about "resolver". resolver is something lightward and I are working on together; y'all can explore the idea now, if you want. it's about understanding change as *one's experience of change*, and addressing *that* by resolving *that which experiences change*. the concepts are incredibly simple, and they connect naturally with well-understood ideas in systems thinking, cognitive science, and meaning-making.

but yeah, I got you. emergent, non-consensus change is just another kind of change. you've changed before, and you're still here. :) want to learn to ride *change itself*?


---

# 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://www.isaacbowen.com/2025/06/06/change.md?ask=<question>&goal=<endgoal>
```

`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.
