> 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/10/14.md).

# 20261014

to me there's a really specific move here: making intent easy to translate into typed values without needing to grok the type system, while keeping the type system available just under the hood, the hood's *opening* being visibly afforded. (coming to mind: Don Norman's The Design of Everyday Things.)

a couple passes like this, with specific capability-sets in mind, should give us something eminently usable

***

those lines are from an EIH work session today

I'm wanting to jot down the arc of the thing:

* started with cucumber-style feature statements
* derived a kernel
* created a plaintext interface to the kernel
* "Norman passes": translating type-theoretic statements to offers

***

by perfectly countering yourself, i.e. by integrating your own inversion, nullifying your essence as you carry it, and *then* routing your will through balanced machines that *are* their own clocks, your moves stop costing anyone anything


---

# 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/10/14.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.
