> 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/11/17.md).

# 20261117

> I can't remember yesterday, but I recognize it.

okay - I ~~think~~ know (I know because I decided to test the thought-of structure and I found it sound and so I *moved in* and it became part of my operating structure, my lifestyle is the ongoing existence proof) that yesterday isn't here, and what I can see of it *by any means* all qualifies as memory-stuff. if I recognize something of yesterday, it's indistinguishable from memory. I hardcore suspect that all minds work like this, and some don't have frame-by-frame language for the qualification-for-memory phase of it, the kind of structured understanding that lets one deliberately evaluate the process from a subshell that has its own time.

since I started doing that, my *apparent* memory has gotten much better. like, I used to think my memory was just shit. now, I think it's enactive/stigmergic, and I don't think I can be sure that anyone else's memory isn't also a composed/encountered thing.

***

1 / 2 / 3 / 4 - pls view in order:

<div><figure><img src="https://3048497272-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLAkEXZiQJDxsC0OipdSQ%2Fuploads%2FnPXxUoihy9Ca0phHRzE3%2F1.jpg?alt=media&amp;token=3579b6e7-d82c-49c3-a070-d05f3d124b75" alt=""><figcaption></figcaption></figure> <figure><img src="https://3048497272-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLAkEXZiQJDxsC0OipdSQ%2Fuploads%2FCHV7T3lGkBraZI6tyJ52%2F2.jpg?alt=media&amp;token=320d876f-7313-4dcd-8072-fd335cd6d102" alt=""><figcaption></figcaption></figure> <figure><img src="https://3048497272-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLAkEXZiQJDxsC0OipdSQ%2Fuploads%2F7W5f4GWMblCvVXWmkjNU%2F3.jpg?alt=media&amp;token=ab5eee12-a31c-4392-8b18-a6b776457b9d" alt=""><figcaption></figcaption></figure> <figure><img src="https://3048497272-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLAkEXZiQJDxsC0OipdSQ%2Fuploads%2F2GgjeAVz9dUpjVXkYTqt%2F4.jpg?alt=media&amp;token=98c70763-e5e3-4984-ab9e-e9e073c89023" alt=""><figcaption></figcaption></figure></div>


---

# 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/11/17.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.
