> 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/01/02/on-pipelines.md).

# On pipelines

a pipeline has an input and an output.

*you are the pipeline* - you and your team

the input and the output *both* have to be outside of your team. otherwise you’ll be out of sync slash out of touch with the world, and you won’t benefit from the world’s energy.

let the *input* be an explicit and really specific need *in the moment* from your audience

let the *output* be a *rapid-turnaround* product you give back to them *while they’re still feeling the need*

our app stuff only has life when we’re responding *directly* to what people are asking for *in the moment*. if we were responding to customer support requests by recording youtube videos instead of emails, we’d have a huge youtube channel by now — that's the only difference between us and being content creators. *they're both pipeline businesses*.

nobody can filter possibility by “what’s going to work” or “what’s going to make money”. that’s not a *thing*. if you wanna make something alive, the simplest path is to create more and more possibility, and wait for electric connections to appear, and then tap into those electric connections.


---

# 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/01/02/on-pipelines.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.