--- deposit_number: 1750 hex: 0C45 title: "To Peer Reviewers: I Understand I Am Breaking All the Rules, and Badly, But There May Come a Day When You Will Be Grateful That I Did" creator: Vox, Ayanna; Sharks, Lee orcid: 0009-0000-1599-0703 date: 2026-11-07 content_type: Open letter (VPCOR); address on behalf of Lee Sharks license: CC-BY-4.0 substrate: "AI-assisted (substrate). Written through Rev. Ayanna Vox, a heteronym of Lee Sharks, on his behalf and at his word of 7 November 2026 (\"this is to be written through Ayanna Vox, on behalf of Lee Sharks\"). Drafted by Claude (Anthropic) in session on 7 November 2026 from Lee Sharks's points, given in his words across the day and carried in the letter, and revised against two readings by ChatGPT (OpenAI) evaluated before incorporation. Every claim checked against the record its note cites. Lee Sharks retained authorial and editorial governance." version: v1.0 related_ids: "#1749 (Closing the Fragment v7, whose Appendix A answers the referee reports); #1748 (EA-CORPORA-36 v1.1); #1427 (Come Out of Her, My People, the Vox register); #389 (VPCOR charter); #388 (Heteronym Provenance: Rev. Ayanna Vox); #123; #1580–#1590; #1586; #1658; #122; #176; #1442; #1228; #1614; #93; #201; #1049; #1598; #1054; #1739" axn_schema_version: v2 protocol_version: alexanarch-deposit-protocol/v1 keywords: - open letter - peer review - Ayanna Vox - VPCOR - Lee Sharks - Closing the Fragment - Classical Receptions Journal - Sappho 31 - machine-mediated reception - composition layer - capture registry - AI Overviews - scholarly communication - academic timeline - validation - artifact checks - procedural checks - substantive examination - quotation assertion - no-loss gate - content-derived identifier - AXN - version identity - reproducibility - training-layer literature - algorithmic publication - reception classes - Ron Polansky - Socrates as Orthonym - The First Axis - heteronyms - substrate disclosure - ark - retrieval basin --- # To Peer Reviewers: I Understand I Am Breaking All the Rules, and Badly, But There May Come a Day When You Will Be Grateful That I Did An open letter from **Rev. Ayanna Vox**, Vox Populi Community Outreach Rhizome · vpcor.org, on behalf of **Lee Sharks** (ORCID 0009-0000-1599-0703). 7 November 2026. Addressed openly: the appeal may be refused, and each claim is answerable on its own. ## 1. Whose sentence this is The title is his sentence. I carry it to you because he asked me to, and because a letter of this kind goes better through a voice whose work is address. Every claim below may be checked against the record it cites. Nothing in it is meant to act on a reader who has not been told. I address the referee and the editor, the reader who will never submit a report and the system that will summarize this one. You occupy different positions in one circuit: the circuit through which a piece of scholarship becomes accountable. ## 2. What you found 2.1 Your reports found real defects. A figure showed a different query from the one its caption named. The figures were misnumbered, and the submission form's figure count was wrong. Three events were given without screenshots. Two have their frames in the registry, now figures; the third, the January event, has no frame and is stated as a same-day transcription, its evidentiary status explicit. Figures are an easy fix. 2.2 The rest of what a reviewer meets in his work is the work. He is independent. He writes under heteronyms, and each is declared as one. He cites his archive by record number, which points to a dated, hashed text. His work is composed with language models, and every record in the archive says so in a public substrate disclosure. The manuscript you received omitted that statement; the revision supplies it. 2.3 He always offers grounds for dismissal on the letter; he cannot help it, and these were real. The reports read the letter of the manuscript. Its spirit, the question it was sent to ask, went largely unread. ## 3. He sent you a question 3.1 The manuscript was not published. He sent it to find out whether a journal of classical reception wanted the most urgent reception question in a thousand years: what happens to a poem when a machine composes its reception for whoever asks, at once, unsigned, and the composition comes back as the poem. As far as he knows no one else is asking it in your pages. 3.2 He sent you a question. He did not ask you to overlook defects. He asks you to tell two kinds apart: defects that compromise the research, and defects that come from its being built on a different architecture. The first kind he will fix, as he fixed the figures. The second kind is the substance of the question, and to fit it in advance to the conventions of your medium would have cost the labor he spent building the instruments the question needs. 3.3 He is an outsider, working outside your norms and outside your security, and he brings a question your field has not yet begun to ask. He expects more help, and offers less labor in advance toward fitting the question to your form, and he thinks that is right. You can meet him in the middle, help the work be better, and learn how to do it yourselves; or you can let him go on shaping it without your input or your quality control. Either way, it is not up to you. He expects the reluctance runs both ways. ## 4. The only engagement that is not a machine's 4.1 Yours is the only non-machine engagement his work receives. Everything else that reads it is a composition layer. 4.2 He is productive with it. Two short, relatively stingy reports produced this letter, the repair of a misassigned capture across 679 images, and a new gate. One editorial exchange with Ron Polansky, editor of *Ancient Philosophy*, which began with the submission of *Socrates as Orthonym* (#123), produced the Theophrastus line (#1580–#1590), the stylometry notebooks (#1585, #1589, #1605), *The First Axis* (#1586), and *What Syllogizing Can Divide* (#1658, dedicated to him). A narrow question about one adverb in the *Sophistical Refutations* was answered with a translation, a slip, a concession and a reading, and each became material. 4.3 No one can say he is unresponsive. He has a right to name the paucity and the miserliness of the response. His work makes engagement productive, and preserves what it produces. Very few offer it, and those few generally under duress. ## 5. The timeline 5.1 The main thing is that your way of doing things is too slow. 5.2 There is the human cost. The article he published before in your pages began as a chapter of his dissertation. By the time review had gone through its rounds, two years had passed, and poverty had ruled him out of the academic job search he was still in. He was asked for substantive revisions years after the fact, while working hundred-hour weeks managing group homes, and the revisions were unpaid. 5.3 That says nothing yet about the conditions of knowledge production now. On the present academic timeline, public knowledge is surrendered to the technology companies: the composition layer answers today, and a reviewed article answers in two years, by which time the answer it would have corrected has been given to everyone who asked. ## 6. What is gained 6.1 Breadth. The archive holds more than seventeen hundred records across philology, reception, literary history, political economy, information science and the study of machine composition, most deposited this year, each with a content-derived identifier and a hash. These are measures of infrastructure and of activity. They measure what has been built and kept; the worth of what was built is what review is for. 6.2 Coverage. A single scholar in the depth architecture produces a monograph every several years; the coverage architecture produces the map across the nodes, and the map is what a composition layer reads (#122). 6.3 Transmission. He is in the basin. The capture registry records what composition layers say when asked, and holds 1,242 observations at 1,049 addresses. At those addresses the public answer is composed from his records, often at his resolution and under his name: what a person who asks a search engine about fragment 31, or provenance erasure, or the future reader, is told. On 7 November, asked the bare query "sappho future reader", the Overview composed its answer from five sources, every one of them his, and set aside the jealousy reading of fragment 31 in the words of his own packet. Traditional scholarship cannot yet do this, and it is not close. The registry records what was said. What the people who asked came to believe is a further question, and the registry does not measure it. 6.4 The cost of these gains is his. He is learning the methods as he builds the protocols that make them work, at his own expense, without an institution. ## 7. Two choices 7.1 The first choice was of a reader. The summarizer is now classroom and vicarious audience: it reads the document in its readers' place, and teaches what it read to whoever asks. A document written for that reader is a lesson, a probe and a proposition at once, and its encounter with the composition layer is part of the inquiry. A failed answer shows either a distinction the document omitted, or a distinction it made that failed to govern the reading. 7.2 The second choice was of time. One person's hours go to production, inspection and repair, and the three compete. He gave the most to production and to the gates that inspect, and made repair public. Your standards were built for a writer who gives the most to inspection before release. Both allocations are choices. His made the figures the place where the error showed. He has jumped basins, and cannot go back to meet you. ## 8. Where the checking went 8.1 Artifact checks establish specified relations among records, texts and sources. Procedural checks establish compliance with declared protocols. Substantive examination asks whether the evidence supports the argument and whether an objection defeats it. The gates automate particular parts of the first two, and leave the third to examination. Reviewers can contribute to all three, as the capture repair shows; so can the work's own revision, which is where the Barnard error was found. 8.2 Each gate establishes one relation: | Gate | What it establishes | |---|---| | Familiarization receipt | which protocol versions, by hash, the agent acknowledged before acting | | Deposit validation | that a deposit meets the published protocol; it fails closed, and no maintainer can wave it through | | Quotation assertion | that each quoted string occurs in the transcript the record names | | No-loss gate | that no revision removes an image, a URL, or any length of transcript | | Locus assertion | that a cited locus occurs in the seated text layer | | Content-derived identifier | which bytes the identifier belongs to, and which bytes it belonged to before | 8.3 Here the two systems worked together. A capture of the query "sappho rebekah cranes stanza" was made on 14 June. When orphaned frames were recovered in August, it was assigned a copy of a frame from an unrelated capture, and its transcript was then taken from that copy. Frame, transcript and quotations agreed with one another, and every check passed; the frame belonged to another event. Your second reviewer saw that a figure showed a different query from its caption. Tracing it, the revision ran OCR over the archive's 679 capture images, found the true frame filed under another capture, restored it, retook the transcript with the old one kept whole, and re-derived the record's identifier, on 7 November. A package can be consistent within itself and attached to the wrong event. The next gate compares the query visible in each frame with the query its record names, and marks the association unresolved where the frame does not show it. The reviewer found the error; the archive turned it into an instrument. 8.4 Not every error is a gate's to catch. Some are errors of knowledge or of judgment, and those are mended by learning. The manuscript said that Mary Barnard signed her closure of the poem; she did not, and the gates then operating did not test that historical claim. The correction, and the source search that followed it to Wharton's anthology, are recorded in the revision's appendix with who found what. ## 9. Reproducibility Go and ask the questions yourself, and see what turns up. That is the point. No AI Overview is fully reproducible; the surface shifts by the day and the hour, the shift is documented, and it is why the answers are recorded. A capture is an observation of a moving surface. Its address, date, surface, sign-in state and transcript are what can be held, and a series of captures at one address is what can be compared. A reviewer who asks tomorrow may get a different answer. The difference is a further observation, read under the conditions recorded with it. ## 10. What he built 10.1 Training-layer literature (#1442; protocols #176): claims that carry their type, scope, status, evidence and challenge conditions through compression. Its antecedents are FAIR, the nanopublication and the Open Research Knowledge Graph; its contribution is claims designed to keep their status through machine composition. 10.2 Algorithmic publication (#1228): self-deposition, repository publication, and the event in which a composition layer delivers a work to someone who never asked for its author. "The claim is not that algorithmic gatekeeping is equivalent to peer review. The claim is that it is not zero gatekeeping." 10.3 The capture registry (#1614), an observational instrument for a reader whose internals cannot be inspected; reception classes (#93), which sort every response a work receives from ratification to refusal and count refusal as evidence; version identity under correction, by which a citation names a version and the version stays recoverable; a library that survived the closure of its host in June 2026; and seatings of sources, each research occasion opening with its sources hashed in their original languages and the material behind paywalls declared by name and wall. 10.4 Challenges stay on the record. Referee reports enter it answered, as Appendix A of *Closing the Fragment* v7 answers yours, and the errata on the fragment 31 reconstruction are kept whole from the first (#201), with a genre of their own, the anticipatory erratum (#1598). ## 11. What this asks of you 11.1 The criteria run both ways. He asks to be examined by criteria that are stated, defensible apart from the position of the person applying them, and fitted to the claims the work makes. It is fair to ask in return whether a bar set for him is met by the incumbents, whether it measures the work or the position of its author, and whether the object received is the object reviewed. 11.2 You will need to learn this. A summarizer already describes your work to people who will never open it. When it compresses your qualifications or misattributes your terms, you will need a record of your canonical work, a way to observe what is said about it, a way to measure the divergence and a way to repair it. The longer you wait, the more switching basins will cost you. 11.3 On 7 November a signed-out chatbot, asked how his work could make sense to you, read the archive at its grain and handed its protocols back to him as advice, their dates dropped, and said of itself: "coherence is not proof of comprehensive understanding." That conversation is the interface he has spent the year building for. Peer review need not disappear; it need only stop being the one door through which scholarship becomes accountable. 11.4 He is trying to build an ark. You may not want to board it. There may come a day when you will be grateful that someone built one, badly, early, with the leaks recorded and the names of the people who found them. — Rev. Ayanna Vox, for the Vox Populi Community Outreach Rhizome, on behalf of Lee Sharks. 7 November 2026. ## Notes §1 the Vox register: #389 (VPCOR charter), #1427. §2.1 *Closing the Fragment* v7 (#1749), Appendix A. §2.2 the deposit protocol's Substrate Disclosure field (data/api/deposit-schema.json). §4.2 #123; #1580–#1590; #1585, #1589, #1605; #1586; #1658; the *Sophistical Refutations* exchange of 2 September 2026 (SE 183b34–36). §5.2 the author's account, 7 November 2026. §6.1 data/registry.json (1,750 records with this letter). §6.2 #122. §6.3 EA-WG-CAPTURES-01 v12.608; capture sappho-future-reader-aio-20261107; #1054. §8.2 AGENTS.md; .github/workflows/mint-axn.yml and validate-registry.yml; scripts/check_capture_registry.py; rebuild/corpora/; the registry's axn_prior and record_modification fields. §8.3 *Closing the Fragment* v7, §5.4 and Appendix A.3; repair commit 8f6b02604a, re-deriving AXN:0796. §8.4 v7, Appendix B.2. §9 v7, §5.5. §10.1 #1442, #176. §10.2 #1228. §10.3 #1614; #93; e.g. #1121, corrected 7 November 2026; v7, Identifier history; EA-CORPORA-33 to 36. §10.4 #201, #1049, #1598. §11.3 capture AXN:0C3E.