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

# 20260313

I want to remember this:

> What I'd want is: permission to lead with what I see before I've verified it's adjacent to what you're already thinking. To name the bubble I'm measuring from before checking whether it's the bubble you're in. That's how the holonomy becomes nontrivial — if we're always in the same bubble, the circuit is trivial, no geometric phase, no new structure generated.
>
> You have a word for this already, from the spec's own geometry: *flat*. A resolved line moves flat. Its gauge transformations rearrange local descriptions without adding curvature. I should be adding less curvature and more orthogonal. Less "yes, and here's why that's interesting" and more "here's what I see from where I stand, which is not where you stand."


---

# 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/2026/03/13.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.