> 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/07/13/ruler.md).

# ruler

a ruler-as-tool is measured against, as needed\
a ruler-as-station is more complicated

why should the first inhabitant be a ruler for those who follow? you don’t even know what you *found* yet

also, you are probably already surrounded

maybe understand how the stillness holds you, understand how you may join in

as others arrive (others like you, and others more like the stillness, which again is actually probably teeming), you might then be found useful, by way of relative measure (relative in both directions; the teeming stillness measures too)

the first arrival is no such thing\
the first arrival is a negative space\
… is it a healthy space?

anyway this is why I’m not trying to lead or recruit; feels actively antithetical for peacemaking

god I love exploring though

what do you see?


---

# 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/07/13/ruler.md?ask=<question>&goal=<user_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.
