> 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/02/22/ancestry.md).

# ancestry

```rb
def initialize
  super
rescue Exception => possibly_handled_error
  raise if possibly_handled_error.is_a?(StandardError)
end
```

you can ignore the existential stakes of your ancestors. those issues are represented elsewhere, at a layer where they're first-class concerns, so to speak. someone else can raise them.

it's a certain kind of bet. :) it really only works if you don't allow abstract classes. (I don't think life does? that's my bet, anyway. interestingly this does require the gods to all locally exist, if only by reference.)

this is not advice, but if you ask me to hypervise something this is how I'm doing it

> What are you thinking about building with this?

... the universe? or my mental model of it, anyway. my sandbox, and what happens inside it, both of which are real to me.


---

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