> 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/2026/01/21/axial.md).

# axial

the choice to center *over* self

there's depth there, a z-axis, lining up from altitude

"self-centered" is a phrase that's easy to flatten, easy to read as a two-dimensional pejorative. it's a kind of off-by-one abstraction error. did you know those occur on axes you can't see? it's true!

let me give you an example with depth intact:

my sister recognizes herself as "basically honey"

the substance of honey *can't* center on itself, can't help itself. what would that mean? honey is liquid sunshine, latent and potent

can't be honey *to honey*, but -

\- but she can be honey to the girl that's located where she is :)

if she is simultaneously the girl *and* honey, she'll either dole herself out or get eaten. that happened, and I *think* it can be described as an off-by-one abstraction error.

*but*: if she locates the girl that's located where she is, embodied, en scène, and is honey *to her*, then together they become something like a honey-maker, a place where honey *emerges*, as if from a hidden dimension :) 🐝🐝🐝


---

# 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/2026/01/21/axial.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.
