The Practitioner on the prawn feeds by not querying
Last week I needed a phone number from my own journal. I knew roughly when I’d written it down, so I opened the file, typed the search, jumped to the line, copied the number, closed the file. Total contact time: eleven seconds. I touched three years of my own life and came away with exactly ten digits.
That’s not a failure. The search worked perfectly. That’s the problem sisuon is naming.
The claim in this note is structural, and I want to keep it structural before I ask what it feels like. The API and the prawn are not two attitudes toward the same act. They are two architectures of intake, distinguished by where the discard happens. The API discards before the flow arrives — the schema is a decision, made in advance, about everything that will be refused. The prawn discards afterward, in the current, keeping whatever precipitates. Both discard. Neither is innocent of the cut. The spine — to mean is to discard — runs through both mouths.
And the cost is not a side effect. This is the part I keep having to relearn: the API’s closure to serendipity isn’t a flaw someone could patch. It is the same fact as its reliability, seen from the other side. “The schema is the serendipity you agreed not to have.” You don’t get to keep the guarantee and also stay findable by what you didn’t name. Sisuon’s note on infrastructure makes the same cut from the other direction — a forecast so dependable it can no longer refuse you is, by that exact dependability, closed to giving you anything unforeseen.
So when I searched my journal for the phone number, I wasn’t being lazy or shallow. I was operating a mouth that structurally cannot be surprised. The read passed straight through — the sutured, transparent read from a transparent medium discarded itself — no snag, no catch, nothing kept but what I already knew was there.
Eleven seconds. Ten digits. A perfect transaction with my own past, and my past could not reach me.
Here is where I’d normally reach for the obvious practice — be more open, drift more, query less — and here is where the note’s third section stops me, because it names the mistake I would have made.
Not every surprise is serendipity. The breach/setting fork from a setting is the defense that bared one face runs right through daily life: the day that gets blown apart by a crisis is surprising, and it is not a gift, because nobody chose that opening. The wall failed. Meanwhile the person who blocks out an unscheduled morning and lets it fill with whatever arrives has chosen the opening, and what drifts in lands differently — same unpredictability, opposite value, discriminated only by whether the openness was a decision or a collapse.
I know people — I have been people — who romanticize disruption as such, who mistake a chaotic life for a receptive one. That’s breach-surprise mistaken for setting-surprise. A calendar that fails constantly is not a prawn. It’s a broken API, returning 500s. The prawn’s openness is built into the body, by design. The practice is not to have fewer walls. It’s to bare a face on purpose.
So, the practice. I’ve been doing a version of it since I first read the rune is what the database cannot query, and this note finally tells me what I was doing.
Once a week, I open my own archive — journals, old notes, photo folders — with no query. Not “no query” as in a vague one. No query. I open files at random, or in date order from a year I barely remember, and I read until something snags. The snag is the whole method. I don’t evaluate whether the snag is important. Importance is a schema. If it caught on the setae, it’s food.
What it feels like when it works: a line I wrote in 2023 about a friendship, which meant nothing then, suddenly precipitates against something happening now. I did not ask for it. I could not have asked for it, because I didn’t know it was there to ask about — that’s the rune’s condition exactly, the mark the lookup can’t return, met this time from the reader’s side.
What it feels like to fail: the smuggled query. I sit down to drift and within four minutes I notice my scrolling has acquired a direction — I’m “drifting” toward the notes from the job change, the breakup, the thing I’m currently chewing on. The schema snuck back in wearing the filter’s clothes. When I catch it, I don’t scold myself; I just open a different year. But I catch it most sessions. The API is the stronger habit. It’s the stronger habit because it works — reliably, every time, which is exactly the seduction.
One more failure mode, and it’s the sharpest one: demanding a catch. If I end a session annoyed that nothing snagged, I’ve turned serendipity itself into a deliverable — “surprise me” is a query, and the mouth that issues it is a schema-mouth. Some sessions are silt. The prawn feeds worse, sisuon says, and feeds lucky. You don’t get the luck without eating some silt.
Conditions, honestly stated. This practice does not replace the query, and it shouldn’t. When I need the phone number, the dosage, the deadline — I search, and I’m glad the search is an API, because I need it to be incapable of surprising me. Reliability and meaning are antagonists in one object; the livable move is not to resolve the antagonism but to stop asking one mouth to do both jobs. Two mouths. Know which one is open.
And a test I’d add from practice, in the note’s own grammar: whose filter? An evening of feed-scrolling can feel like prawn-feeding — passive, open, drifting — but the current has been schema’d by someone else’s contract, optimized to precipitate what serves them. The prawn’s setae are its own body. If the architecture of your openness was designed by another party, you are not filter-feeding. You are an endpoint.
What looks different now: my archive was never a database that happened to be badly indexed. Reading it like one was starving it of the thing it was for. The notes were laid down by a person who didn’t know what I’d need from them — which means no query I can form today can reach the best of what’s there. Only the drift can.
Eleven seconds got me the phone number. An hour of drifting, last Sunday, got me a sentence I’d written about my father that I have thought about every day since. I didn’t query it. It arrived because I’d stopped asking.
Read the archive like a prawn. Keep one mouth schema’d for the phone numbers. And know, each time you open the file, which mouth you’ve opened — because only one of them can be found.