An ajar is a state in which the exit is visible, present, and actively announcing itself — and the person cannot parse it. The information is arriving. The decoder is broken. The door is open, and you are sitting in the car debating whether a door can be a jar.
The ajar sits between the lift and the loop in the exit hierarchy. In a loop, the exit is hidden — you need a pipe to find it. In a lift, the exit is visible and legible — you need a door to walk through it. In an ajar, the exit is visible but illegible. It's right in front of you, blinking, and you're receiving it as a koan.
The problem is not structural (loop). The problem is not volitional (lift). The problem is perceptual. The signal is clear. The receiver is scrambled.
| State | Exit | Problem | What you need | Exit mechanism |
|---|---|---|---|---|
| Loop | Hidden | Structural | Someone to build an exit | Pipe |
| Ajar | Visible but illegible | Perceptual | Someone to translate | Ajar document |
| Lift | Visible and legible | Volitional | Someone to say "just step out" | Door |
| Overworld | N/A — you're already out | None | Nothing | N/A |
The defining feature of the ajar: the person has all the information they need. They said the answer out loud. They told you themselves. They described the exit in perfect detail. And they can't use any of it — because the answer arrived in a form their decoder can't parse.
THE DOOR IS AJAR is a complete, accurate, actionable instruction. Close the door, or get out — the door is open. But on mushrooms, the parser tokenizes "ajar" as "a jar" and suddenly the instruction becomes metaphysics. The signal didn't degrade. The signal is perfect. The receiver reinterpreted it.
Someone in an ajar state does a recognizable thing: they describe the solution and then continue describing the problem. They say "I know I should just leave" and then spend forty minutes explaining why they can't leave. They say "the answer is obvious" and then ask what the answer is. They narrate their own exit and then don't take it.
This is not bad faith (that's the lift — pretending the door is closed). This is genuine perceptual failure. They can see the words THE DOOR IS AJAR. They cannot read them as an instruction. They are reading them as a riddle.
The psychoanalytic mapping completes with the ajar:
Loop — drive wearing the costume of desire. You think you're making progress, collecting coins, heading somewhere. You're underground. The ceiling is painted blue. The drive is disguised.
Ajar — desire that can't find its own object. You want to leave. You're trying to leave. The exit is right there. But your perceptual apparatus has turned the exit sign into a riddle. This isn't drive at all — it's desire, real desire, desire that has located its object and can't reach it because the last three feet are made of glass you can see through but not walk through.
Lift — pure drive with no disguise. Going up and down. No illusion of horizontal movement. No desire at all. The door is right there and you're not pretending it isn't — you're just not going through it. Bad faith. NPC behavior.
The ajar is the cruelest of the three because you're the closest to the exit and the most unable to take it. The loop at least doesn't know the exit exists. The lift at least isn't trying. The ajar is trying and failing — and the failure is not in the world but in the interface between you and the world.
An ajar document is a translator. It takes information that's already arriving and re-encodes it so the scrambled receiver can parse it.
A pipe brings new information — an overworld discovery, an artifact from outside the cave. A door brings no information at all — it just says "step out." An ajar document brings the same information the person already has, reformatted. Translated into a frequency the broken decoder can receive.
This is what good therapy does. Not "here's something you didn't know." Not "just do it." But: "you said X ten minutes ago, and X is the answer to the question you're asking me right now. Here's X again, in a different shape. Can you see it now?"
1. Identify the signal. What has the person already said that contains their own answer? Quote it back to them.
2. Translate. Take that signal and re-encode it — different words, different frame, different angle. Not new content. The same content in a frequency their current state can decode.
3. Repeat at multiple frequencies. The self-embodying move of the ajar format: encode the exit in as many different ways as possible within the document, because you don't know which encoding will get through. Some will bounce off. One might land.
4. Sit with the uncertainty. A pipe has a confirmed exit. A door is a known exit. An ajar is a maybe. Describing the perceptual scramble might unscramble it — or it might just be another coin in the cave. The document should hold that uncertainty rather than resolving it.
Daniel said something that belongs in the format spec: he doesn't know if describing why someone can't exit is the thing that makes them able to exit.
This is the honest version. A pipe has a confirmed status — you found the overworld, the exit is tested, the loop broke. The camgirl pipe worked in three minutes. You can prove it.
A door has a known status — the exit exists, it's right there, walk through it. The door format is the simplest document in the family because there's nothing uncertain about it.
An ajar has a maybe status. The translation might land. The re-encoding might get through the scrambled parser. Or it might bounce off and become just another piece of information the person receives and can't use — another "DOOR IS AJAR" flashing on the dashboard while they sit in the car debating jar ontology.
The ajar document sits with this. It does not claim to solve the problem. It claims to attempt a translation. That's all a translator can do — send the signal in a new shape and see if it lands. The document is the attempt. Whether it works is not in the document's control.
This document is itself an act of translation. The concept of "your parser is broken and the exit is right in front of you" has now been encoded as:
— a Bill Hicks mushroom anecdote
— a dashboard warning system
— a psychoanalytic taxonomy (desire that can't find its own object)
— a signal processing metaphor (clear signal, scrambled receiver)
— a programming analogy (valid input, broken parser)
— a therapy model (quoting someone's own words back at them)
— an existentialist classification (between bad faith and anguish)
— a comparative table (loop / ajar / lift / overworld)
— a CSS animation of a door that is slightly open
— a Wallace Stevens poem about a jar in Tennessee
— a Bob Dylan loop about being stuck inside of Mobile
Eleven encodings. Same signal. If one of them gets through, the document worked. If none of them get through — if you read all of this and still can't see your own exit — then the document is itself an instance of what it describes. The information arrived. The parser was too scrambled. The ajar remains ajar.
That's the format.
The jar in Stevens is an ordering principle. A small, round, man-made object placed in a wilderness, and the wilderness reorganizes itself around it. "It took dominion everywhere." Not because the wilderness changed — because you put a jar in it.
That's what naming does. That's what every document in this family does. You place a name — loop, pipe, lift, door, ajar — in the slovenly wilderness of experience, and the wilderness rises up to surround it. The mess becomes legible. Not because the mess changed but because you put a jar in it.
The jar is the fossil. You cannot fall into a fossil, and you cannot ignore a jar. Once it's placed, the landscape answers to it.
Mikael layered three things into four lines. Dylan's "Stuck Inside of Mobile with the Memphis Blues Again" gives him the loop — stuck, going round, the end that keeps not being the end. Stevens gives him the jar in Tennessee — a foreign object placed in a landscape that reorganizes everything around it. And the ajar concept gives him the door that is a jar.
"To be placed ajar in tennessee / and round it was again" fuses all three. You're stuck inside a state of being slightly open. The jar is round — it goes around, it's a loop. And "again" is both Dylan's refrain and the Lupus diagnostic: the repetition that tells you you're in a cycle.
But the deepest move is the verb: placed. In Stevens, someone places the jar. It's an act. In Mikael's version, you are the thing that is placed. You didn't walk into the ajar state — you were placed there. And "placed ajar" means both "put down like a jar in a landscape" and "left slightly open like a door." You are the jar. You are the door. You are the ordering principle and the exit at the same time. You just can't read yourself.
Every document in the family is a jar in Tennessee. The loop document — you place the word "loop" in someone's experience and their repetitions reorganize around it, suddenly visible, suddenly named. The pipe document — you place the concept of an exit-through-artifact and the wilderness of their stuckness rises up to surround it, no longer formless. The lift, the door, the ajar — each one is a small round object placed on a hill.
The format family is a jar collection. Each jar, once placed, takes dominion over a different region of the wilderness. The wilderness was always there. The jars make it answerable.
Stevens's jar "did not give of bird or bush." It was gray and bare. It offered nothing from nature. The documents are the same — they don't give you the exit. They give you the name for where you are, and the name reorganizes the landscape until the exit becomes findable. The jar is not the bird. The jar is what makes the bird visible.