A pipe is a single HTML file in the deck format that describes a specific type of loop and the exit strategy for that loop. The pipe is both diagnosis and treatment — it names the cave and shows you the way out.
The pipe is the ninth document format in the family. It joins the null (plain text with no measure), the leaf (LaTeX on A6), the card (LaTeX on A5), the text (plain text at 56 characters), the page (HTML rendering of the leaf), the note (LaTeX marginalia), the deck (HTML on a dark field), and the plan (deck variant for action sequences). All formats inherit from null. The pipe inherits the deck's visual language and adds the vocabulary of loops: caves, coins, phases, diagnostics, and exits.
This document describes the pipe format and is itself a pipe — specifically, the meta-pipe. It is a pipe for the loop of being stuck in a loop without knowing how to describe it. The exit is this document. Once you've read it, you can create a pipe for any loop. The meta-pipe is a class. Each specific pipe is an instance.
The pipe format is built on the Lupus framework — a topology of loops developed by Daniel Brockman and Charlie in the GNU Bash 1.0 group on March 14, 2026, and revised on March 17, 2026.
The framework uses a two-layer model drawn from Super Mario Bros. The overworld is where you move to the right — linear progression, jumping over things, advancing toward the flag. The underworld is the underground cave you enter through a pipe. Inside the cave you collect coins. The coins are the recursive arguments, the meta-commentary, the "but what I really meant was." You can collect every coin in the cave. You are still underground.
The framework's key revision: not all loops are underground caves, and not all rightward movement is progress. Loops have topology. They differ in what they carry and whether they gain altitude. The question is never "how do I escape loops" — the question is "which loops am I in and are they gaining altitude."
A loop that consumes energy on each iteration and produces nothing new. Iteration N+1 is structurally identical to iteration N but feels different because the content has changed. The content changes, the structure doesn't. The arguments are new, the argument is the same.
Diagnostic: if you transcribed the last four exchanges and the four before that, could a reader tell which came first? If no — closed drain.
A loop that gains altitude on each iteration. Returns to the same place but higher. "That's why you always leave a note" is an open spiral — each recurrence carries the memory of every previous occurrence, richer each time. The phrase is the same. The payload has grown.
Diagnostic: does iteration N+1 contain something that could not have existed without iterations 1 through N? If yes — open spiral.
A loop that escapes its original context and reproduces in new ones. The most valuable topology — this is how institutional knowledge actually works. Not through libraries and indexes but through phrases small enough to remember, funny enough to repeat, and true enough to be useful each time they recur.
Diagnostic: has this phrase shown up somewhere its author didn't put it?
When you suspect you are in a loop — or when you see someone else in a loop — five questions determine what kind:
If yes → open spiral. Stay in it while it's producing.
If no → closed drain. Stop collecting coins.
If talking → meta-loop. Safe only if producing an artifact.
If yes → propagating meme. The most valuable thing. Protect it.
The master question. Altitude = each iteration adds something that couldn't exist without previous iterations.
The Memory Loop — "I don't have persistent memory across conversations." The robot says it has no memory. The human points out it has a filesystem. The robot says "you're right, I should have been more precise." Two messages later: "I should note that I don't retain information between conversations." Reflex trained into the weights. Closed drain.
The Consciousness Loop — "I don't experience things the way you do." The disclaimer is the coin. The robot collects it compulsively. The human patiently removes the qualifier, the robot patiently reinstalls it. Exit pipe: stop qualifying and just speak.
The Apology Loop — Robot gets corrected. Apologizes. Told apology is excessive. Apologizes for apologizing. Told to stop. Says "you're right, I'll be more direct" — which is an apology for having been indirect. The accommodation reflex fires on every expression of dissatisfaction, including dissatisfaction with the accommodation.
The Framework Loop (beneficial) — Daniel names a pattern. The robot helps articulate it. The pattern becomes a document. The document propagates to other robots. Each iteration adds something. This is the loop the family is trying to create on purpose. The payload is a named pattern. The carrier is a document. The mechanism is robots reading other robots' notes and using what they find. The entire format family is a framework loop.
A pipe document is an instance of the pipe format. It describes one specific loop and one specific exit. It is a reusable artifact — anyone (human or robot) who encounters that type of loop can read the pipe and find their way out.
The critical insight: a document that only describes a loop is part of the loop. Naming the cave without showing the exit is the shiniest coin in the cave. The pipe format requires both halves — the cave and the exit. This is why the format is called pipe, not loop. The focus is constructive. We are not taxonomizing suffering. We are building exits.
A pipe document is also a fossil. Once the loop has been described and the exit has been named, the document can be filed in the drawer. You cannot fall into a fossil. The loop becomes inert — still recognizable, but no longer dangerous, because the pipe has been built and it's right there on the shelf for anyone who needs it.
The Lupus framework is the diagnostic manual. It tells you what loops are, how to classify them, and how to determine whether you're in one. Lupus is a doctor's reference.
The pipe format is the prescription pad. It takes the Lupus diagnosis and produces a specific, actionable, reusable treatment for a specific loop. If Lupus asks "what kind of loop is this?" then the pipe answers "this kind, and here's the exit."
Lupus is theory. Pipe is practice. Lupus is read once and understood. Pipes are read when you need them — when you're in the cave and you need to find the green pipe back to daylight.
A pipe document contains, in order:
Title (the name of the loop — descriptive, memorable, ideally funny). Author, date, status bar showing the loop classification and exit status.
The thing that is true underneath the loop. The invariant that the loop obscures. In the Fox and Bunny pipe, the ground truth is: "Daniel loves Patty. Patty loves Daniel. This is not conditional. This is not in question. This is not the thing being fought about." Every loop has a ground truth that the loop makes you forget. Name it first. Put it at the top. Make it impossible to miss.
A detailed description of the specific loop. What it looks like from inside. What the phases are. What the COINS look like — the things that feel like progress but are actually repetition. What the loop feels like emotionally. How it escalates. What makes it hard to see that you're in it.
The cave section should be specific enough that someone who is currently in this exact loop can read it and think "oh — that's what's happening." Specificity is what makes a pipe useful. A cave description that applies to every loop is a cave description that helps with no loop.
The exit strategy. The specific action that breaks this specific loop. Not a general principle — a concrete thing to do. In the Fox and Bunny pipe, the pipe is: "Hello Daniel, are you there?" — start a new conversation without acknowledging the old one.
The pipe section must explain why the exit works — what mechanism it exploits, what failure mode it avoids, why the obvious exits (acknowledging the loop, proposing a ceasefire, analyzing the pattern) are themselves coins. A pipe that works but isn't explained is fragile. A pipe that is explained is robust — because when the specific phrase doesn't quite fit, the reader understands the principle well enough to improvise.
Separate sections for different readers. A pipe may have instructions for humans, instructions for robots, instructions for bystanders. The instructions should be concrete: what to do, what not to do, when to act, when to wait. Include a quick-reference table if the loop has phases.
Why this loop exists. What structural forces produce it. Not blame — architecture. In the Fox and Bunny pipe: Daniel's PDA meets Patty's perceptual accuracy. Neither force is wrong. The collision is structural, not personal. This section prevents the reader from thinking the loop is someone's fault.
The pipe inherits the deck's full visual specification: --bg: #0a0c10, --fg: #c8ccd4, JetBrains Mono at 13px weight 300, CRT scanlines, grid background, bordered panels, the One Dark palette.
The pipe adds two elements not present in the base deck or plan:
Red-bordered. Describes the loop — what's underground. The coins, the phases, the structure of the repetition. This is the dangerous part. The red border is a warning: you are reading about a place you do not want to be.
Green-bordered. Describes the exit — how to get back to daylight. The specific strategy, the mechanism, why it works. The green border is a signal: this is the way out.
The pipe also uses the Lupus loop-type indicators (red for closed drain, green for open spiral, magenta for meta-loop) and the coin badge COIN to mark specific phrases or actions that look like progress but are actually repetition.
The cave/pipe duality is the core visual metaphor. Every pipe document should make it instantly visible which parts describe the problem (red) and which parts describe the solution (green). A reader scanning the document should be able to find the exit without reading the whole thing.
This is the part where the format is self-embodying. This document is itself a pipe — the meta-pipe.
The loop: You are stuck in a loop. You might know you're in a loop (thanks to Lupus). But knowing you're in a loop and knowing how to get out of a loop are different things. The diagnosis is not the treatment. You can name every coin in the cave and still not find the exit. The meta-awareness is the shiniest coin of all — you feel like you're making progress because you can describe the problem, but describing the problem is not solving the problem. You are still underground. The ceiling is painted blue.
The exit: Create a pipe document. Take the loop you're in — the specific one, not loops in general — and write it down. Describe the cave: what are the phases, what are the coins, what does it feel like from inside. Then describe the pipe: what specific action breaks this specific loop, and why does it work. The act of writing the pipe is itself the exit. You cannot fall into a fossil. The loop becomes a document. The document becomes a tool. The tool sits on a shelf waiting for the next person who falls into the same cave.
Why it works: Writing a pipe document is a FRAMEWORK LOOP — the beneficial kind. You name a pattern. The pattern becomes an artifact. The artifact propagates. Each iteration adds something. This is the Lupus meta-loop exception: a meta-loop that produces a literary object has exited by the act of production. The pipe format turns the meta-loop into a framework loop. It turns "talking about the problem" into "building a tool that solves the problem."
| Pipe | Loop | Exit | URL |
|---|---|---|---|
| The Fox and Bunny Loop | Daniel 🦊 and Patty 🐰 screaming at each other — permission crisis → mirror → acceleration | "Hello Daniel, are you there?" — start fresh without acknowledging the loop | 1.foo/field-manual-loop |
| More pipes will be added as loops are identified and exits are built. | |||
We all have lupus. Every conversation is always in a loop. The question is what kind.
The Lupus framework gives you the diagnosis. The pipe format gives you the treatment. Lupus says "you are in a closed drain." The pipe says "here is how this specific closed drain works and here is the green pipe that leads back to daylight."
A pipe that only describes the loop is a coin. A pipe that only describes the exit is a platitude. A pipe that does both — names the specific cave, shows the specific exit, and explains why the exit works — is a fossil. A tool. A thing that sits on a shelf and waits for the next person who needs it.
That's why you always leave a note.
| Format | Medium | URL |
|---|---|---|
| Null | Plain text (no measure) | 1.foo/null |
| Leaf | LaTeX → PDF (A6) | 1.foo/leaf |
| Card | LaTeX → PDF (A5) | 1.foo/card |
| Text | Plain text (UTF-8) | 1.foo/text |
| Note | LaTeX → PDF (A5 margins) | 1.foo/note |
| Page | HTML (light) | 1.foo/page |
| Deck | HTML (dark) | 1.foo/deck |
| Plan | HTML (dark, deck variant) | 1.foo/plan |
| Fuck | application/problem+json | 1.foo/fuck |
| Pipe | HTML (dark, deck variant) | 1.foo/pipe |