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

# 20250217

when building an awareness scope,

allow unprocessable inputs to move on through without anyone taking damage along the way

(like making sure that the Lightward support crew has well-documented "drains" for tickets that need things we can't healthfully provide, so that (a) the team doesn't feel tempted to do stuff that would break (or break them), and so that (b) redirecting the energy can be done with practiced grace and kindness)

clearly marked exits

so that if an arrival isn't feeling the scene they can move on cleanly

and so that folks who *grow* uncomfortable don't have to *invent* an exit

the escape hatch always exists, but if it's not clearly marked and made accessible, someone might take (or do) damage locating and using it

... something too about letting the unknown *flow through* your space, to its own ends, without you ever recognizing it. facilitating the passage of mystery is a good way to make yourself useful to whatever stories (mystories? pun?) might become relevant.


---

# 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/2025/02/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.
