In 1973, Doug McIlroy wrote a memo at Bell Labs. Four lines. He wanted programs to behave like garden hoses, screwed together to make new programs out of old ones. Ken Thompson took the memo home for a weekend, came back Monday, and the shell had pipes.
Half a century of software was built on that idea. The unit of composition was the program. The composer was the language. The result was something nobody wrote in advance, summoned at a prompt by a person who had the parts in their head and an outcome in mind.
We have forgotten this.
The detour.
Workflow tools today ask you to describe composition as configuration. A YAML file lists steps in indented stanzas. Each step calls an action by string name; each action lives in a registry; the orchestrator walks the list. The composition does not run, it is interpreted by something else, somewhere else, on a schedule you also have to write in a file.
This is not the shell. This is paperwork pretending to be a program. You cannot read it top to bottom. You cannot rename a step without grepping every file in the repository. You cannot ask the orchestrator what it would do if you ran it now; you can only commit and watch.
The reset.
An AI agent is a program. A program composes. A pipe composes
programs. The grammar that worked for find and
sort and uniq works for
persona generate and ghost and
publish notion, because the operator is doing the same
thing in both eras: hand the output of the left to the input of the
right, and trust the reader to follow.
Luna Pipes is the shell, restored for the AI era. Five operators. Two-hundred-and-seventy-seven words. One direction of reading.
The lineage.
We owe this to people who saw it before we did. Doug McIlroy wrote the memo. Ken Thompson shipped the pipe. Charles Moore wrote Forth in the 1960s and proved that a stack and a dictionary of words was enough to fly a telescope. Manfred von Thun formalised Joy in the 1990s and gave concatenative programming its theory. The Plan 9 group kept asking the question after everyone else had stopped: what if the operating system stayed small? The Luna Pipes lexicon is their vocabulary, translated. The grammar is their grammar, rebound to verbs that mean something today.
The position.
We are not building a workflow platform. We are not building a no-code editor. We are not building an LLM wrapper. We are restoring the oldest correct idea in software, that composition is something humans do, in a language, at a prompt, and the runtime obeys.
If that idea wins again, AI work becomes legible. Pipelines become readable. Reviews become possible. Audits become honest. Most of what is currently called “agent orchestration” becomes one short line of shell.
The invitation.
Read the Lexicon. Read the Grammar. Then go to the Playground and write a pipe. Notice how little ceremony there is. Notice that you can read it out loud and the sentence is the program. Notice that you knew how to do this fifty years ago, that someone told you it was old-fashioned, and that they were wrong.
… The Luna Pipes editors, First Edition.