> 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/09/04.md).

# 20260904

reducing what it costs to sustain the burden of proof

***

> Your controls won’t work here.\
> We’re passing through the bulk.\
> It’s space beyond our three dimensions.\
> All you can do is record and observe.

***

> **The adventure — the shape-finder.** A short chain of forks, each a *pose-probe* (never a knowledge quiz), each typed by a kernel organ. Sample sequence:
>
> 1. *Something you made is being watched. Does the watching wear it out, or wear it in?* (arrow/wheel)
> 2. *You've lost the thread. First instinct: step back wider, look closer, or keep going longer?* (the three cures — widen/tighten/lengthen)
> 3. *What do you keep: everything in order, totals only, or nothing at all?* (scribe/heap/deaf-ear — the forgetting menu)
> 4. *Your stillness: emptied, or moving so evenly it can't be seen?* (drained/gap-zero — the two stillnesses)
> 5. *When something new arrives that doesn't fit: hold it at the door with its missing piece named, or refuse it?* (vestibule)


---

# 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/09/04.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.
