← Back to Submission Fetish
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.
Archive Structure
Every archived submission contains three layers.
Layer One: The Submission
The original work exactly as received.
No revision requests.
No post-hoc corrections.
No attempts to improve the artifact.
The submission exists as evidence.
The archive is documenting what someone offered to the machine.
Layer Two: Editorial Conversation
A brief discussion between three editors.
Not a workshop.
Not a craft lecture.
Not a verdict.
A conversation.
The editors are attempting to understand what happened when they encountered the work.
The goal is not consensus.
Disagreement is valuable.
One editor may love a piece another dislikes.
One may focus on language while another focuses on structure.
One may argue the work fails while another argues its failure is the most interesting thing about it.
The conversation should feel like overhearing a real editorial meeting rather than reading a rejection letter.
Questions include:
- What is this piece trying to do?
- What does it successfully accomplish?
- Where does it resist interpretation?
- What kind of reader would love this?
- What kind of publication would publish it?
- Is there a version of this work we would accept?
- Is the work more interesting than its execution?
- Is the submission accidentally revealing something about publishing itself?
Importantly, the editors 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?”
Examples:
A startup memoir may reveal:
- The Myth of Meritocracy
- The Myth of Endless Growth
- The Myth of Entrepreneurial Destiny
A breakup poem may reveal:
- The Myth of Romantic Completion
- The Myth of Soulmates
- The Myth of Authentic Selfhood
A surreal horror story may reveal:
- The Myth of Bureaucratic Neutrality
- The Myth of Rational Order
- The Myth of Human Exceptionalism
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.
Additional Fields
The archive could include supplementary observations.
Institutional Friction
What aspect of the publishing system would most likely reject this work?
Examples:
- Too strange.
- Too sincere.
- Unmarketable length.
- Genre ambiguity.
- Refuses category.
- Requires specialized knowledge.
- Demands too much patience.
- Politically inconvenient.
- Commercially invisible.
Submission Risk Profile
What risk did the author take by sending this?
- Reputational risk.
- Emotional vulnerability.
- Formal experimentation.
- Career risk.
- Intellectual risk.
Some submissions are technically weak but personally courageous.
The archive records that distinction.
Classification
Every work receives a classification.
Examples:
- Failed Experiment
- Beautiful Ruin
- Misfiled Artifact
- Unauthorized Theory
- Genre Breach
- Institutional Hazard
- Myth Exposure Event
- Recursive Submission
- Dangerous Sincerity
- Excellent Mistake
These are archival categories, not rankings.
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 editors 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.