> 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/ideas/always-leave-a-door-open.md).

# Always leave a door open

Pretty sure this leads to [recursively open doors](https://www.isaacbowen.com/ideas/always-leave-a-door-open/recursively-open-doors.md), btw.

## For people

I'd like to say "assume nothing about each other", but to speak any language at all requires some assumption. (Even if it's the assumption that the other person can *hear*.) We have to make *some* assumptions about what we're up for, but always leave a door open for someone to say "hey, I want something else".

## For product

When making a product, ensure that it is *at its core* infinitely reconfigurable, infinitely flexible, in such a way that a configuration of the product can work around limitations in the product itself.

[Tripartite systems](https://en.wikipedia.org/wiki/Three-body_problem) are great for this. (Locksmith has locks, keys, and key conditions; Mechanic has events, tasks, and actions.)

{% hint style="info" %}
This concept is mentioned in:

* [20231223](https://www.isaacbowen.com/2023/12/23.md)
  {% endhint %}


---

# 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/ideas/always-leave-a-door-open.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.
