> 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/2024/04/04/10-20am.md).

# 10:20am

*scene: AK's car, AK's driving, Abe's in the front passenger seat, I'm behind him, we're leaving West Hollywood for Laguna Beach for the day*

me: I'm — lol, I have words to say and they're making me laugh — I'm experiencing back seat joy! hahaha I'm just really enjoying being taken for a ride

AK: hahahahaha that's so true! and metaphorical!

It was while recording the above words that I looked out the window and saw this piece of public art in a streetside park:

<figure><img src="https://3048497272-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLAkEXZiQJDxsC0OipdSQ%2Fuploads%2F8Oew0DOtWyvERDpSvy6i%2FJI8A9474%20c-2.jpg?alt=media&amp;token=780c2cd6-6a4f-4407-a9f8-86db9fa6b529" alt="" width="340"><figcaption></figcaption></figure>

> Catalan-Spanish artist Jaume Plensa has exhibited all over the world and installed major public artworks throughout Europe and the Americas. His work addresses the condition of humanity in a world enmeshed in technology – a mixed condition, as the symbolism of so many of his objects indicates. Language, “the first technology,” has a double-edge for Plensa, being the medium for poetry and song but also for Babel-like division and misunderstanding. Plensa’s ideal human, like this figure, embraces all languages, familiar and foreign. Among the eight tongues represented here are English, Spanish, and Hebrew.
>
> <https://publicartarchive.org/art/Endless-V/0ac77ac0>


---

# 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/2024/04/04/10-20am.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.
