← Back to Submission Fetish · or see How the Archive works
What makes the Submission Fetish archive interesting is that it is not just archiving texts. It is archiving the encounter between a text and an institution.
Most literary magazines preserve only the accepted work. Some preserve the rejected work by accident, buried in email inboxes and Submittable databases. Submission Fetish preserves the entire event.
A submission is treated as an artifact.
The artifact includes:
- The work itself.
- The editorial encounter.
- The institutional response.
- The mythological machinery operating beneath both.
The archive is less interested in whether a piece is “good” than in what happened when it entered the system.
Two Findings, Not One Grade
Before the layers, the two findings printed at the head of every entry. They answer different questions and are constantly mistaken for one another.
Disposition
Settled at intake, in a line, and never revised. What the machine did with the artifact on arrival.
Retained — the artifact goes on the record and is processed.
Refused — off the record entirely.
Refusal is reserved for spam, plagiarism, work whose primary ambition is cruelty, and work that mistakes cynicism for insight. Nothing else is refused, and a refused artifact leaves no file at all — which is why this is not a museum of rejections either.
Retention is not approval. It is evidence.
Retention Status
Assigned after processing, revisable forever, and not a ranking of quality. It measures how deeply the artifact penetrated the machine that received it — four rungs, earned by effect rather than merit.
- Archive — a meaningful encounter that left the machinery unchanged. Most work lives here, and living here is not a failure.
- Residency Candidate — something has begun to recur. Contamination suspected, not proven.
- Permanent Resident — the archive demonstrably reads or operates differently because this came through.
- Systemic Code — it rewrote the rules by which later artifacts are processed. Carries the gold mark, Foundational Myth. Rare by definition.
Both findings are printed on the piece’s own page, beside its form and its volume, where a conventional magazine would print a date.
Publication is not a reward.
Residence is a condition.
The promotion test for each rung is set out in what residency means; the ladder is drawn whole on the Field Diagram, and its current occupants are listed in the residency.
Archive Structure
Every published entry carries three layers, in this order, under headings the reader meets on the page: the work, What the readers said, and Why it is here, and what it reaches for.
Layer One: The Submission
The original work exactly as received, published in full. Nothing waits in a drawer, and nothing is excerpted.
No revision requests.
No post-hoc corrections.
No attempts to improve the artifact.
Transcription is the one place the archive touches the text, and it is bounded. Manuscript chrome — running headers, page numbers, submission-format debris — is not part of the poem and comes off. Encoding corruption is repaired, because mojibake is a transmission fault rather than something the author wrote.
Everything else stays. In poetry the archive assumes intent: a lowercase sentence-start, a repeated word, an unclosed quotation mark, a capital mid-line, a fragment with no subject. In prose these would be errors. In a poem they are decisions until the poet says otherwise.
The archive transcribes.
It does not tidy.
Anything that would require guessing what the author meant is put to the author rather than settled here, and the author okays the piece before it is printed. What appears on the page is the text they ratified, not a house version of it.
The submission exists as evidence. The archive is documenting what someone offered to the machine.
Layer Two: The Readings
Three readers. Three readings, filed separately and independently. They are identified by initials only — SV, AR, ML — with no role titles and no declared lens, so that a reading is met as a reading rather than as the output of an assigned position.
Not a workshop.
Not a craft lecture.
Not a verdict.
Each reader is attempting to say what happened when they encountered the work, in their own prose. A filed reading is one clear point carried by its evidence, quoting the piece and letting the quotations do the arguing. Said once, in the fewest words that keep it true, and then stopped. Where two readers close on the same detail, it belongs to one of them.
There is no questionnaire, and there are questions the readings deliberately do not ask: whether there is a version of the work the archive would accept, what other publication might run it, whether the piece is good. Those are acquisition questions, and disposition was settled at the gate.
The goal is not consensus.
Divergence is not a problem to be resolved. It is a measurement — evidence that the work is exerting pressure on its readers.
One reader may find the machinery of a piece where another finds only its weather.
One may hold that the work fails where another holds that its failure is the most interesting thing about it.
One may go looking for a system and report that there was nothing there.
The divergence is not staged for the reader and it is not resolved on the page. It is left standing.
That last case has a name. A Zero Spike is what a reading files when an artifact forces a reader off their usual obsession and there is nothing further to say — no fracture, no system, no ghost. It is a finding, not the absence of one: the archive stops rather than theorize past the literal, which is why a filed reading will sometimes say in plain language that it went looking for something larger and found nothing there. Absence of effect is a valid result. The archive does not intensify a finding because the form expects intensity, and when nothing happened the record says so without softening it. Forcing a Zero Spike is grounds for promotion up the retention ladder.
The readings should feel like overhearing three readers who have each just put a file down, rather than reading a rejection letter. They are written in ordinary sentences, to be read by the person who wrote the piece.
Importantly, the readers are not pretending to be objective.
They are part of the archive.
Their reactions are artifacts too.
Layer Three: The Myth Audit
The Myth Audit examines the ideological and narrative infrastructure operating inside the piece.
Not whether the author intended it.
Whether it is present.
Every text emerges from myths.
Some reinforce them.
Some expose them.
Some become trapped inside them.
Some cannot decide.
The Myth Audit asks:
“What stories about reality must be true for this text to exist?”
It names three things, in this order.
The exposed myth — the belief the piece puts under pressure, written as a belief a person might actually hold rather than as a capitalised abstraction. Not The Myth of Cultural Capital, but the belief that paying to look at something means you understand it. A myth named in theory-language has been filed away; a myth named in ordinary language is still recognisable as something someone believes on a Tuesday.
The dependent myth — the one the piece uses without examining, because it needs it in order to work. This is frequently the more damaging of the two, and the archive records it as a dependency rather than a discovery: it is what the text takes as settled, not what the text found.
The symbolic target — the object the piece appears to be assembling, named in a phrase. This is the line printed on every entry under The myth it reaches for: the audit as confession, the gate that is also a verdict, the quilt that no one wove.
With them go the piece’s symbols — drawn from its own objects, each glossed in plain language — and its themes. Both appear as chips at the foot of the entry.
The audit is not a moral judgment.
A myth can be exposed, reinforced, complicated, satirized, mourned, or worshipped.
The point is to identify the machinery.
The section closes with the retention rationale — why the artifact is held at the rung it is held at, in that rung’s own register. Rung is not rank, and the record says so on the page rather than leaving the reader to infer a ranking that was never made.
What the Archive Ultimately Studies
Traditional publishing asks:
“Should this be published?”
Submission Fetish asks:
“What happened here?”
What happened when this writer decided the work was finished?
What happened when they sent it?
What happened when three readers encountered it?
What happened when institutional expectations collided with the text?
What myths became visible during impact?
The archive is not a museum of successful literature.
It is a field station documenting collisions between language and permission.
Every submission leaves debris.
The archive studies the debris.