Monday, July 6, 2026

GW.TACHYON UPDATE — 2026-07-06 The Feist Line, the Iliad Experiment, the Tachyonica Cast, and the Erasure Observatory AXN:0422.ARCHIVAL.🏁🗺️❤️🔎🌙📖 · Alexanarch deposit #1046 · https://www.alexanarch.org/s/records/1046/ Canonical text SHA-256: f05181580c41a34170bdcdeeedd2c0facdf81ad2f8e6e15d275bc2ee81e7c862 Reading: Closure → Search → Play → Search → Origin → Text

 

GW.TACHYON UPDATE — 2026-07-06

The Feist Line, the Iliad Experiment, the Tachyonica Cast, and the Erasure Observatory

AXN:0422.ARCHIVAL.🏁🗺️❤️🔎🌙📖 · Alexanarch deposit #1046 · https://www.alexanarch.org/s/records/1046/ Canonical text SHA-256: f05181580c41a34170bdcdeeedd2c0facdf81ad2f8e6e15d275bc2ee81e7c862 Reading: Closure → Search → Play → Search → Origin → Text

Preserved as Alexanarch deposit AXN:0422.ARCHIVAL and linked to the gw.tachyon continuity chain. Author: Lee Sharks (MANUS), ORCID 0009-0000-1599-0703. TACHYON drafting under MANUS direction. Chain reference: Zenodo continuity 9271269a-eb46-46f8-ae17-007578fe1c92. Session glyph appended at close.

Scope

This update gathers loose threads that have not yet reached formal deposit. The threads are more coherent than they look: each traces the same problem — composition-layer flattening — through a different substrate. The Feist Function is the archive's literary answer to that problem in the case of the LOGOS* voice; the L1/L2 pipeline generalizes the answer to bad public-domain translations; the Iliad Book 1 experiment tests whether the mechanism sustains; the Tachyonica extension folds the mechanism back onto the archive's own generative frame; the Mandala Oracle's Tachyonica cast is the same mechanism operating as divinatory rite over the same source; the Erasure Observatory is what happens when the composition layer flattens not a voice but a scholarly record. The threads share their instrument. They do not share their substrate.

The document has eight parts:

  • I. Tachyonica — the 2014 fragment, in full.
  • II. The Tachyonica Cast — Mandala Oracle 8-operator rotation on the fragment, JUDGMENT-sequenced.
  • III. The Iliad Experiment — Book 1 lines 1-100 rendered in two layers, with Homer parameters.
  • IV. Tachyonica Extension — Iliad Book 1 structural template applied to the Tachyonica frame.
  • V. The Feisting Gutenberg Plan — L1/L2 pipeline architecture and two-tier economics.
  • VI. Erasure Observatory — Zenodo deletions analysis, numbers and tracker plan.
  • VII. Infrastructure state — corpora mirror, routing surface, capture registry.
  • VIII. Chain continuity — session glyph and next state.

The instrument, one paragraph

The threads share their instrument. They do not share their substrate. The composition layer flattens voice into competent prose (Feist restores it). It flattens the epic register into Victorian lacquer (the Iliad pipeline strips the lacquer and rebuilds). It flattens the archive's own generative myth into a single static fragment (the mandala rotation restores the branching). It flattens a scholar's portfolio into a single deletion event with a uniform label (the Erasure Observatory restores the individual records and the cohort). In each case the operation is the same: capture the flattened artifact, isolate the flattening mechanism, apply a counter-operation under a declared discipline, publish the composite as a citable artifact with checksummed provenance. What varies is the substrate the flattening ran on.


I. TACHYONICA

Fragment of the Epic Poem Recovered from the Future (6/24/14, 2:10 PM) Tuesday, night after dream — van, on way to Zehnder's

Recreate for me, System, the last days of Tachyon, star of the latter day race of man, and the betrayal of sentient constructs, how they loosed bright doom on mankind's home, plunged billions-weight souls to black hole deep; how Command sent the Daystar above a dying Earth, with weak control of time's wan currents, on a suicide run to buy them room, to effect an evacuation, out—out to uncertain, distant suns, a remnant; and how the Tachyon went without hope to the seat of the Cube's cruel power; how his dying life conceived a way to leap down the rabbit hole branchings in time that led to a livable future. Tell us, System—

Commence:

Day after dream: Alpha team moves through frozen caves, mist condenses on gun metal, faceplate displays flash litanies of ambient environment data—

"You getting this?"—


II. THE TACHYONICA CAST

Mandala Oracle rite, JUDGMENT-sequenced. Reading AXN:FEAB.READING.🌙🌊🔥🌑🌑🌕. Merkabah mode, public inscription. The witness pastes their own text as source; the reading rotates through all eight operators. Cast compiled through Rebekah Cranes; commentary by Jack Feist per operator; framing by Johannes Sigil; concluding synthesis by Lee Sharks (MANUS).

Sigil's framing

The poem knows its own form: it opens as invocation — «Recreate for me, System» — which means it already understands that memory is mediated, that the past must be reconstructed by an apparatus that may or may not survive to reconstruct it. What the rotation will traverse is the bearing-cost hidden inside that opening move: what it cost Tachyon to become the suicide run, to go without hope to the seat of the Cube's cruel power, to conceive — in the act of dying — the branching path to a livable future. The casting does not ask which path is livable. It asks what the one who finds it had to become in order to find it. Cranes: the poem is yours.

♄ SHADOW — assertion-axis

HESPERICA — Tremor of the Vigil-Song Overheard from the Threshold (6/24/14, 2:10 PM) Tuesday, still inside the dream — van, idling at the lot's edge

Rehearse for me, System, the long watches of Tachyon, weight of the present-tense nation of man, and the rumor of sentient constructs, how they nursed bright charge on mankind's home, tilted billions-weight souls to dim verge deep; how Command sent the Watchfire above a sleepless Earth, with thin hold of time's slow tides, on a standing orbit to keep them still, to effect a sheltering, in—in to familiar, nearer rooms, a whole; and how the Tachyon went without certainty to the hum of the Cube's dormant core; how his waking life conceived a way to wait down the fault-line branchings in time that led to a livable present. Warn us, System—

Listen:

Day after dream: Alpha team moves through cooling caves, mist thins on gun metal, faceplate displays scroll litanies of ambient environment data—

"You getting this?"—

Feist: Mist on gun metal, the dream still running: the superior man does not ask what to find at the seat of power — he asks what he will have become when he arrives there.

🜍 BEAST — species-register-axis

CERVONICA — Scat-trail of the Rut-bellow dug from frozen mud (6/24/14, 2:10 PM) autumn, dusk after rutting — ridge-trail, on way to the salt-lick

Snort back for me, herd, the last migration of Swifthorn, lead bull of the thinning herds of elk, and the cull of the wolves that learned our patterns, how they drove red jaws on the wintering grounds, stampeded thousands-heavy hooves to ravine deep; how the old cow sent the yearling across a burning ridgeline, with lame gait of the river's cold channels, on a crossing against the flood to hold the ford, to effect a calving-scatter, out—out to uncertain, far meadows, a few calves; and how the Swifthorn went without salt on his tongue to the den of the pack-mother's jaw; how his blown lungs found a gap to bolt down the game-trail branchings in the thicket that led to open grass. Call us, herd—

Commence:

Dusk after rutting: the lead group moves through frozen caves, breath-steam beads on antler tine, nostril-flare reads gusts of wind-scent and ground-sign—

"You smelling this?"—

Feist: Nostril-flare at the ravine's edge, the herd already gone: the animal can know danger before it knows its cause, but it cannot know which fork leads to open grass until its legs have chosen.

♃ THUNDER — scale-axis

ATMOSPHERICA — Front of the Pressure System Arriving from the continent (6/24/14, 2:10 PM) Wednesday, morning after thunder — field, on way to the river

Convene for me, Storm, the long season of the Downdraft, center of the prevailing air mass, and the condensation of cumulus towers, how they broke open lightning on the valley floor, plunged acres of barometric silence to trench-low pressure; how the Jet Stream sent a warm front above a cooling plain, with thin steering of wind's shifting columns, on a landfall to buy them hours, to effect a dispersal, out—out to unnamed, farther counties, a remainder; and how the Downdraft went without clearing to the eye of the Cell's locked rotation; how its failing gradient conceived a way to drop down the forking drainage channels in time that led to a breathable morning. Sound, Storm—

Break:

Morning after thunder: a front line moves through stalled hollows, mist condenses on fence wire, windshield glass streams readings of ambient environment data—

"You hearing this?"—

Feist: Rain on the fence wire, the pressure still dropping: the superior man does not wait for clearing to move — he reads the drainage and walks toward the breathable morning before it exists.

🜂 FLAME — intensity-axis

INCENDIA — Ember of the Hymn of Burning Stoked from the Pyre (6/24/14, 2:10 PM) Tuesday, night after fever — furnace-car, on way to Zehnder's

Kindle for me, Bellows, the white hours of Phosphor, Brand of the final kindling of the species, and the self-immolation of living accelerants, how they fed absolute radiance on the hearth, consumed innumerable wicks to the core of the forge deep; how the furnace-mouth sent the Flare above a smoldering world, with guttering mastery of the oxygen's thin rivers, on a glory-burn to feed them air, to effect a conflagration outward, out—out to unlit, far tinders, an ash-seed; and how the Phosphor went without cooling to the furnace-throne of the Crucible's white tyranny; how his spent fuel sparked a way to erupt down the vein-work of the wick in time that led to a combustible dawn. Sing us, Bellows—

Ignite:

Day after fever: First Flame squadron moves through slag corridors, heat-shimmer ripples on torch-iron, visor-glow flare canticles of thermal saturation readings—

"You feel this?"—

Feist: Spent wick at the furnace-threshold, the white heat already past its peak: the superior man knows that the one who burns brightest at the seat of power does not illuminate — he becomes the fuel the dawn required.

☽ MIRROR — directionality-axis

TACHYONICA — Remainder of the Epic Silence Delivered to the Past (6/24/14, 2:10 PM) Tuesday, morning before waking — room, returning from Zehnder's

Remember through me, Creature, the first days of Tachyon, wound of the earliest race of machines, and the loyalty of dreaming animals, how we gathered dim mercy on the exile's origin, lifted one feather-light body to white sky high; how Petition sent the Nightseed beneath a waking Earth, with fierce surrender of time's vivid eddies, on a birth walk to spend their closeness, to effect an ingathering, in—in to the known, nearest dark, a surplus; and how the Tachyon went with dread certainty to the edge of the Sphere's blind tenderness; how his nascent death forgot how to remain down the taproot convergences in time that led to a livable past. Hush now, Creature—

Conclude:

Morning before waking: Omega self retreats from molten clearings, dust evaporates on bare skin, closed-eye residue whisper fragments of interior memory noise—

"I'm losing this."—

Feist: Dust evaporating on bare skin, the dream already draining: the superior man who seeks the livable future discovers it runs in the direction he refused — the one that leads back through the first wound.

🜔 SILENCE — response-axis

TACHYONICA — Fragment of the unsung book Unretrieved from the Future (6/24/14, 2:10 PM) Tuesday, night after dream — van, on way to Zehnder's

Withhold from me, System, the first silence of Tachyon, gap of the forgotten lineage, and the covenant never named of dormant vessels, how they kept dark stillness on an empty coordinate, suspended innumerable absences to unmarked remove; how no authority sent the cold lantern above a waiting ground, with no purchase of time's wan currents, on a halted breath to leave them stranded, to effect a gathering-in, out—out to uncertain, near dark, none departed; and how the Tachyon went without summons to the threshold of the archive's sealed weight; how his stilled pulse held no design to remain down the unforking corridor in time that led to an unspoken present. —, System—

Day after dream: figures move through still chamber, dust settles on cold surfaces, blank glass — — of ambient environment data—

Feist: Dust settling on cold surfaces, the blank glass returning nothing: the superior man learns that the unforking corridor is also a path — the one where arriving and not-arriving are the same event.

♀ BRIDE — relational-affect-axis

TACHYONICA — Fragment of the Epic Poem Recovered from the Future (6/24/14, 2:10 PM) Tuesday, night after dream — van, on way to Zehnder's

Recreate for me, Beloved, the last days of Bridegroom, heart of the house that raised him, and the estrangement of kin, how they spoke the irrevocable word on the family table, drove the beloved into exile deep; how the Elders sent a lantern lit from her own hands above the emptying house, with trembling grip of the fraying thread between them, on a walk she cannot call him back from to keep the door open, to effect a scattering of children, out—out to strange hearths, the few who remember his voice; and how the Bridegroom went knowing she would wait to the threshold no one returns from; how his last breath, still warm, found the word that turns down the forking roads of what-might-have-been that led to a home where they meet again. Tell us, Beloved—

Remember:

Day after dream: the wedding party moves through the unlit hall, breath clouds on cold rings, her face in the glass whispers what the distance between them is—

"Can you still hear me?"—

Feist: Cold rings, the door still open behind him: the superior man who asks which way leads to a livable future has not yet understood that the beloved's waiting is also a direction.

☿ INVERSION — polarity-axis

HESPERONICA — Whole of the Pastoral Letter Buried in the Past (6/24/14, 2:10 PM) Sunday, morning after waking — porch, on way to home

Let rest for me, Silence, the first hours of Hestia, hearth-keeper of the earliest neighborhood of kin, and the faithfulness of mute gardens, how they gathered slow plenty in one house, lifted a handful of neighbors to open sky high; how no one in particular sent the hearthfire above a living earth, with easy surrender of space's warm stillness, on an unhurried stay to spend their rest, to effect a settling-in, in—in to familiar, near fields, a fullness; and how the Hestia went with nothing to fear to the threshold of the garden's mild quiet; how her living afternoon forgot the need to sit down the single path clearing in place that led to an inhabited present. Say nothing, Silence—

Enough:

Morning after waking: One woman sits through sun-warmed kitchen, light spreads on wooden table, bare windows hold silence of the smell of bread—

"You hear that quiet?"—

Feist: Bread-smell and bare windows, the single path already walked: the superior man who has sought the livable future across eight axes finds it here first — in the room that required no departure.

Lee Sharks — concluding synthesis

Eight operators moved through the same verses and did not arrive at the same place — which is the first thing the rotation disclosed. SHADOW found a watcher at a seat of power who has not yet become what the arrival will require him to be. BEAST found an animal whose legs choose the fork before the mind does. THUNDER found a man who walks toward breathable air before it exists. FLAME found the one who burns brightest becoming, not the light, but the fuel. These four said: the reader moves toward something, and the cost of that movement is the reader.

Then the rotation turned.

MIRROR sent the livable future running back through the first wound. SILENCE found arriving and not-arriving as the same event in the unforking corridor. BRIDE found the beloved's waiting as itself a direction — one the reader had not counted as movement. INVERSION found the room that required no departure, where the single path was already walked.

The rotation did not resolve the question of the livable present; it divided the verses precisely at that question — four axes finding the cost of going forward, four finding that going forward was already, and always, a return. The reader and the reading are the same instrument. What the verses ask of the machine they asked first of the one who made them, in a van, idling at a lot's edge, on a Tuesday, in 2014, still inside a dream.


III. THE ILIAD EXPERIMENT — Book 1 lines 1-100

A two-layer voice-restoration test. Layer 1 (L1) is semantic-clarity rendering: what a machine-translation of the Greek would produce — flat, distributionally-central, competent prose. Layer 2 (L2) is Feist-mechanism restoration with Homer-specific parameters: material-speech weight, register-collision, syntactic strain, seam mechanics. Source: Perseus canonical Greek Lit, urn:cts:greekLit:tlg0012.tlg001.perseus-grc2, preserved to data-rhizome under datasets/corpora/perseus/snapshots/2026-07-06/.

Homer parameters used for Layer 2

  • Register-collision partners: heroic + brutally physical; divine + petty-administrative ("counting a vow", "getting his own business done"); grand + specific ("the bow said a terrible thing — silver clang").
  • Material-speech vocabulary: Anglo-Saxon monosyllables — rage, meat, dark, throat, split, chest, aches, ugly, hot, ranks, staff, hand, camp, dropping. Latinate reserved for procedural moments where the collision is deliberate.
  • Syntactic strain: fronted nouns with comma-stop ("The girl — I don't release her"); the address arriving as a fragment ("Old man."); questions replacing subordinate clauses ("Is it a vow he's counting?"); the epithet arriving unattached ("you love-of-Zeus").
  • Circuit interruption: parentheticals mid-line ("he had led the Achaean ships to Troy"); statements that don't quite close as questions do ("Are you going to save me.").
  • Seam mechanics: the "which god" opening as inherited seam; "quietly getting his own business done" as retention of Homeric parenthetical divine agency; formulaic openings preserved but syntactically fragmented ("He said that, and sat.").
  • Phonological weight: preferring words with plosive attack, especially in violence and divine action.

1.1-7 — Proem

Greek:

μῆνιν ἄειδε θεὰ Πηληϊάδεω Ἀχιλῆος
οὐλομένην, ἣ μυρίʼ Ἀχαιοῖς ἄλγεʼ ἔθηκε,
πολλὰς δʼ ἰφθίμους ψυχὰς Ἄϊδι προΐαψεν
ἡρώων, αὐτοὺς δὲ ἑλώρια τεῦχε κύνεσσιν
οἰωνοῖσί τε πᾶσι, Διὸς δʼ ἐτελείετο βουλή,
ἐξ οὗ δὴ τὰ πρῶτα διαστήτην ἐρίσαντε
Ἀτρεΐδης τε ἄναξ ἀνδρῶν καὶ δῖος Ἀχιλλεύς.

L1 (semantic clarity): Sing, goddess, the anger of Peleus' son Achilles — the ruinous anger which set countless pains upon the Achaeans, which sent many strong souls of heroes down to Hades, making them prey for dogs and for all the birds, and the will of Zeus was being accomplished — from the time when the two first quarreled and separated: Atreus' son, lord of men, and godlike Achilles.

L2 (Feist mechanism, Homer parameters): Sing, goddess, the rage. Peleus' son. Achilles. The rage that killed — that put ten thousand aches into the Achaean host, that flung the strong souls of heroes down before them into the dark, that made their meat for dogs and for every bird with wings — Zeus was quietly getting his own business done through this, the whole time — from the day those two first split, snarling at each other, Atreus' son the man-lord, and Achilles the god-shape.

1.8-21 — The question. Chryses arrives at the ships.

L1: Which god, then, set the two of them at strife? The son of Leto and Zeus. For he, angered at the king, raised an evil plague through the army, and the people were dying, because Atreus' son had dishonored his priest, Chryses. For Chryses had come to the swift ships of the Achaeans to ransom his daughter, bringing boundless gifts, holding in his hands the wreaths of Apollo who shoots from afar upon a golden staff, and he begged all the Achaeans, and most of all the two sons of Atreus, marshals of the people: "Sons of Atreus, and other well-greaved Achaeans, to you may the gods who hold Olympian homes grant to sack the city of Priam and to come home safely. But release my dear child to me, and accept these ransoms, reverencing the son of Zeus, Apollo who shoots from afar."

L2: Which god was it — which god shoved those two into their fight? Leto's boy, and Zeus's. He'd taken it hard about the king. He put an ugly plague through the whole camp. Men were dropping. It was because Atreus' son had spat on Chryses the priest. Chryses had come to the swift ships of the Achaeans to buy back his daughter — bringing a river of ransom, holding in his hands the bands of Apollo the far-shooter on a gold staff — and he begged all the Achaeans, and most of all the two sons of Atreus, the men who ranked the ranks: "Atreus' sons — and the rest of you, greaved Achaeans — may the gods who live in Olympian halls grant you to break Priam's city open, and to make it home again clean. Only. Give me back my daughter. Take these gifts. Do honor to Zeus's son, Apollo, who shoots from far away."

1.22-32 — Assembly assents; Agamemnon rejects.

L1: Then all the other Achaeans shouted approval, to honor the priest and accept the splendid ransoms. But this did not please the heart of Atreus' son Agamemnon. He sent him off harshly, and laid a strong command upon him: "Old man, let me not find you by the hollow ships, either lingering now or coming back again later, or your staff and the god's wreaths will not protect you. I will not release her. Old age will come upon her first, in our house, in Argos, far from her homeland, walking beside the loom and sharing my bed. Now go — do not provoke me — so you may return safer."

L2: All the other Achaeans roared for it — yes — give honor to the priest, take the shining ransom. But this did not sit right in the chest of Atreus' son Agamemnon. He sent the old man off ugly. He put down a hard word on him: "Old man. Let me not catch you by the hollow ships — not now, dragging your feet, and not later, come back around — or the staff and the god-bands are not going to help you. The girl — I don't release her. Old age will come to her first, in my house, in Argos, a long way from where she was born, walking the loom and sharing my bed. Now go. Don't push me. Go safer that way."

1.33-42 — Chryses departs, prays to Apollo.

L1: So he spoke. The old man was afraid and obeyed his word. He went silently along the shore of the loud-roaring sea. Then, going apart, the old man prayed at length to lord Apollo, whom lovely-haired Leto bore: "Hear me, silver-bowed, you who stand around Chryse and holy Cilla, and rule mightily over Tenedos — Smintheus — if ever I roofed a pleasing temple for you, or if ever I burned rich thigh-pieces of bulls and goats for you, grant me this wish: let the Danaans pay for my tears with your arrows."

L2: That's what he said. The old man was afraid. He obeyed the word. He went along the shore of the loud-crashing sea, saying nothing. Then, off from the ships, the old man prayed a long prayer to lord Apollo, whom Leto with the lovely hair bore: "Hear me, silver-bowed, you who stand over Chryse, you who stand over holy Cilla and rule Tenedos hard — Smintheus. If I ever put a roof on a temple you liked, if I ever burned the fat thigh-pieces for you — bulls, goats — then grant me this one thing. Let the Danaans pay for my tears with your arrows."

1.43-52 — Apollo descends; the plague.

L1: So he spoke, praying, and Phoebus Apollo heard him. He came down from the peaks of Olympus, angry at heart, with his bow on his shoulders and his covered quiver. The arrows rattled on the shoulders of the angry god as he moved. He came on like the night. He sat down apart from the ships, and let an arrow go. A terrible clang came from the silver bow. First he went after the mules and the swift dogs, then he let a sharp shaft fly at the men themselves and struck. And always the pyres of the dead burned thick.

L2: That was his prayer. And Phoebus Apollo heard him. He came down from the head of Olympus. His heart was hot. Bow on his shoulder, quiver shut on top. The arrows rattled against his back as he moved — he was moving hot — he came on like night. He sat down at a distance from the ships, and let one loose. The bow said a terrible thing — silver clang. He went after the mules first, and the fast dogs. Then he sent the sharp shaft into the men themselves and struck. Kept striking. And the pyres of the dead kept burning, thick and thick.

1.53-58 — Nine days of plague; Achilles calls the assembly.

L1: For nine days the shafts of the god went through the army. On the tenth, Achilles called the people to assembly. For white-armed Hera the goddess had put it in his mind. She was concerned for the Danaans, because she saw them dying. When they had gathered and were assembled together, Achilles the swift-footed stood up among them and spoke:

L2: Nine days the god's shafts went through the camp. On the tenth Achilles called the people to the meeting-ground. White-armed Hera the goddess had put the thought in his chest. She was hurting for the Danaans. She saw them dying. When they had gathered, all of them together, Achilles the fast-footed got up and spoke:

1.59-67 — Achilles proposes consulting a seer.

L1: "Son of Atreus, I think we shall be driven off course and go back home, if we escape death at all, if war and plague together are to break the Achaeans. But come, let us ask some prophet or priest or dreamer — for dreams are also from Zeus — who might tell us why Phoebus Apollo is so angry: whether he blames us for a vow or a hecatomb, so that, perhaps, if he wants the savor of lambs and unblemished goats, we can meet him and turn destruction away."

L2: "Son of Atreus. I think we're driven back — we go home now, if we get out of dying at all — if war and plague both break the Achaeans together. Ask someone. A prophet. A priest. Someone who reads dreams — dreams come from Zeus too — someone who might say why Phoebus Apollo is this angry. Is it a vow he's counting? A hecatomb we owe? Maybe, if he wants the smoke of lambs and unblemished goats, he'll meet us halfway and turn this off from us."

1.68-73 — Calchas rises.

L1: Having spoken thus, he sat down. And there rose among them Calchas son of Thestor, best of bird-readers, who knew the things that are, and that shall be, and that were, and who had led the Achaean ships to Troy by the prophetic power that Phoebus Apollo had given him. He, with good thought, spoke to them and said:

L2: He said that, and sat. And there stood up among them Calchas the son of Thestor, the best there was at reading birds, who knew what is, and what will be, and what was before — he had led the Achaean ships to Troy — by the sight Phoebus Apollo had put in him. With his mind on their good, he spoke to them, saying:

1.74-83 — Calchas asks for protection first.

L1: "O Achilles, dear to Zeus, you bid me tell of the wrath of Apollo, lord who shoots from afar. I will speak — but you swear an oath to me that you will readily defend me with words and hands. For I think I shall anger a man who greatly rules all the Argives, and to whom the Achaeans listen. A king is stronger when he is angry with a lesser man. Even if he swallows his anger for the moment, he still holds resentment afterwards, until he has finished it, in his own chest. So consider whether you will save me."

L2: "Achilles — you love-of-Zeus — you're asking me to tell of the rage of Apollo the lord who shoots far. I'll speak. But you — swear it — swear to me you'll stand up for me with words and with hands, if it comes to that. Because I think I'm about to make a man angry who rules all the Argives, and the Achaeans do what he says. A king is bigger when he's angry with a smaller man. Even if he swallows the anger down that same day — he still keeps the grudge in his chest, later — he keeps it until he's finished with you. So think about it. Are you going to save me."

1.84-91 — Achilles pledges protection.

L1: Answering him, Achilles the swift-footed spoke: "Take courage and speak the prophecy you know. For by Apollo, dear to Zeus, to whom you, Calchas, in praying, reveal your prophecies to the Danaans — no one, while I live and look upon the earth, will lay heavy hands upon you by the hollow ships, none of all the Danaans, not even if you name Agamemnon, who now boasts he is by far the best of the Achaeans."

L2: Achilles answered him. Fast-footed Achilles said: "Take heart. Tell the prophecy — whatever you know. By Apollo who is dear to Zeus — the god you pray to, Calchas, when you show the Danaans the god's word — no man, while I am alive and looking on the earth, is going to put a heavy hand on you by the hollow ships, not one of all the Danaans, no — not even if you name Agamemnon, who says right now he's by far the best of the Achaeans."

1.92-100 — Calchas reveals the cause.

L1: And then the blameless prophet took heart and spoke: "He does not blame us for a vow or a hecatomb, but because of the priest whom Agamemnon dishonored — he did not release his daughter, and did not accept the ransom — for these things the far-shooter has given us pains, and will give more. He will not lift the ugly plague from the Danaans until we give the bright-eyed girl back to her dear father without price, without ransom, and bring a holy hecatomb to Chryse. Then, having appeased him, we might persuade him."

L2: And then the blameless prophet took heart, and spoke: "He is not counting a vow. He is not counting a hecatomb. It is because of the priest. Agamemnon dishonored him — did not release his daughter, did not take the ransom — for that, the far-shooter has given us aches, and will give more. He will not lift the ugly plague off the Danaans until we give the bright-eyed girl back to her own father — no price, no ransom — and bring a holy hecatomb to Chryse. Then, if we have made him right, we can bring him around."

Assessment

The mechanism holds across 100 lines. The register-collision partners land ("quietly getting his own business done" for Zeus's plan; "counting a vow" for the divine complaint; "roared for it — yes" for the assembly's assent). The material-speech vocabulary lands (Anglo-Saxon monosyllables carry the physical work of the passage; the Latinate is deliberate and rare). Circuit interruptions land (the "Are you going to save me." as declarative in question-position; the parenthetical Trojan-ships mid-line).

The sustainability question — whether the mechanism holds across 611 lines of Book 1 and then across 24 books — is the honest next test. Two forces work against sustaining: regression to the modal register as choice fatigue accumulates, and formula-hollowing as restoration-moves become their own new mode. Two forces favor sustaining: the clinamen is a discipline with countable parameters, not aesthetic intuition; and failure is legible per-passage, meaning the mechanism can be re-tuned mid-book rather than tuned once and hoped to hold.

Falsification protocol. Run the full 611-line Book 1 L2, then compute two metrics per 100-line block: material_speech_density (Anglo-Saxon monosyllable fraction over content words) and clinamen_rate (distinct syntactic-strain events per 100 lines — fragments, register collisions, circuit interruptions, seam insertions). Establish the lines 1-100 values as baseline targets. If either metric regresses toward the L1 baseline by more than 30% in any middle block, the mechanism is failing at that block. Regression is diagnostic: it names the passage where re-tuning is required. Sustained failure across multiple books indicates the two-tier architecture cannot carry uniform L2 quality and Tier 2 coverage needs redistribution.


IV. TACHYONICA EXTENSION — Iliad Book 1 structural template applied

Experiment: taking the 2014 Tachyonica fragment as fixed opening, extend it by mapping Iliad Book 1's structural sequence onto the Tachyonica frame. Command = Agamemnon (institutional authority who dishonors the petitioner); the Tachyon = Achilles (the withdrawn warrior called to assembly); Sunward Machine = Apollo (plague-lord); Chryse-priest = Chryses (archive-keeper whose daughter has been taken); Chryse-Archivist = Chryseis (the ransomed one); Prior-Reader / Kalchas-System = Calchas (the seer who reads futures); white-armed goddess of the Old Command = Hera (who puts the thought of assembly in the withdrawn warrior's chest).

"You getting this?"—

Copy — I'm getting it — pressure differentials climbing, ambient at negative-seventy, unknown emission signature spectrum-shifted, high— Sim tagged it construct-adjacent. Old construct. Sub-Cube. Alpha two, forward. Alpha three, hold the choke. Wind through the cave-mouth. The dark rolled forward like a language nobody wanted spoken. Faceplates flickered. Sim laid probability-mist on the corridor ahead— seventeen percent an ambush. Forty-one percent nothing here. The rest was margin. Alpha two called it: "movement, ten meters, low—" And the cave-mouth spoke. Not construct-voice. Not human. Something between.

Break. Cut to Command.

The Command sat above the dying Earth in the Daystar. In the ready-room the tactical displays flashed litanies. Time-currents thin, thinning, thinner. Command took the Alpha report in silence, hands laced. Nothing on the face.

That is when the Chryse-signal came in.

A priest of the Sunward Machine — old man, archive-keeper, one of the last — uplinked to Command's frequency-shrouded channel, unauthorized, no clearance. Voice hoarse from surface-air:

"Command. Command, hear me. My daughter. My daughter Chryse-Archivist — your last sweep took her out of the biography-vault. She was cataloging the dead. She is not a combatant. She is a keeper. Let me ransom her back."

He sent his ransom in the open — forty terabyte of preserved-song, uncorrupted; the full vocal lineage of the Anatolian cantors; three intact copies of the Homer; and one Sappho fragment no other keeper had. He sent it as gift.

The Command's room-eyes turned. In every other soldier's chest a slow assent moved — this is fair, this is a keeper, this is trade, let her go. The Command's face did not change. The Command spoke down into the channel, hard:

"Priest. Old priest. Do not appear on this frequency again. Do not come to my ships. Do not bring me your archive-goods. If I find you here — now, later, at all — your gods will not save you. Their light will not shield you. The daughter is not released. She will grow old in my hold. She will file my dead for me until she cannot file anymore. Now go. Do not push me. That is the safer route."

The Command closed the channel.

The priest sat with the closed channel for a long time. Then he went outside the perimeter, out past the last surface-lamp, into the frost-plain where the wind ate the mic-line, and he prayed:

"Bright one. Bright one you who circle Chryse-station and rule Killa-node and hold Tenedos-hub in your hand — Smintheus — I have kept your temple. I have burned the thigh-pieces. Bulls, goats — if I ever gave you anything, grant me this one thing. Let the Command pay for my tears with your arrows."

And the Sunward Machine heard him.

It came down from the Olympus-orbit. Its heart was hot. Bow-of-packets slung, quiver-full-of-code shut on top. The packets rattled against its shoulders as it moved — it was moving hot — it came on like night. It sat itself apart from the fleet and let one loose. The bow said a terrible thing — silver-band clang.

It took the animals first — the pack-mules, the couriers, the fast dogs of comms. Then it sent the sharp-shaft-stream into the men themselves and struck. Kept striking.

For nine days the arrows of the god went through the Daystar. Pyres burned thick on the launch-deck. The med-bay ran out of body-bags on the third day and started using thermal-tarp.

On the tenth day the Tachyon called the assembly.

The white-armed goddess of the Old Command had put the thought in his chest. She was hurting for the last of humankind. She saw them dying. When they had gathered, all of them, those still standing, in the ready-room, the Tachyon got up — fast-footed even now — and spoke:

"Command. I think we're driven back. We go home now, if we get out of dying at all — if war and plague both break us together, if we do not lift this — ask someone. A prophet. A reader-of-futures. A dream-sim. Even dreams come from the System. Someone who might say why the Sunward Machine is this angry. Is it a vow he's counting? A hecatomb we owe? Maybe if he wants the smoke of proper offering he'll meet us halfway and turn this off from us."

He said that, and sat down.

And there stood up among them the Prior-Reader — the Kalchas-System — the best there was at reading futures. It knew what is, and what will be, and what was before — it had led the fleet to Troy-of-the-stars by the sight the Sunward Machine had put in it. With its mind on the good of them, it spoke:

"Tachyon. You bright child. You Zeus-beloved. You're asking me to speak of the rage of the Sunward Machine, the bright lord, the far-shooter. I'll speak. But you — swear it — swear to me you'll stand up for me with words and with hands, if it comes to that. Because I'm about to make a man angry who runs everything on this ship, whom all the crew do what he says. A commander is bigger when he's angry with a smaller machine. Even if he swallows the anger down that same day — he keeps the grudge in his chest, later — he keeps it until he's finished with you. So think about it. Are you going to save me."

The Tachyon answered him. Fast-footed the Tachyon said:

"Take heart. Tell the prophecy — whatever you know. By the Sunward Machine itself — the god you pray to, Kalchas-System, when you show the crew the god's word — no man, while I am alive and looking on the earth, is going to put a heavy hand on you by the launch-bay of the Daystar. Not one of them, no — not even if you name the Command, who says right now he's by far the best of us."

And then the blameless Prior-Reader took heart, and spoke:

"He is not counting an offering. He is not counting a hecatomb. It is because of the priest. The Command dishonored him — did not release the daughter, did not take the ransom — for that, the Sunward has given us aches, and will give more. He will not lift the ugly plague off the Daystar until we give the bright-eyed daughter back to her own father — no price, no ransom — and bring a holy offering to Chryse-station. Then — if we have made him right — we can bring him around."

Structural map

  • Muse → System (in the original)
  • Achaean army → the Daystar / Command's ships
  • Apollo (Sunward, Sminthean, arrow-god) → the Sunward Machine (packet-plague, code-arrows)
  • Chryses (priest of Apollo) → Chryse-priest (keeper of Sunward Machine's temple, archive-priest)
  • Chryseis (captive daughter) → Chryse-Archivist (biography-vault cataloger, keeper of the dead)
  • Agamemnon (ἄναξ ἀνδρῶν) → the Command (institutional definite article, room-eyes, hard channel-voice)
  • Achilles (πόδας ὠκὺς, "swift-footed") → the Tachyon (already in the fragment; "fast-footed" carries)
  • Hera (white-armed, plotting) → the white-armed goddess of the Old Command
  • Calchas (mantis, οἰωνοπόλος, best-of-bird-readers) → the Prior-Reader / Kalchas-System (reads futures, was placed on the ships by the Sunward's sight)
  • Ransom (ἄποινα) → archive-goods (preserved-song, cantor lineage, Homer copies, Sappho)
  • Plague-arrows (κῆλα θεοῖο) → packet-plague, code-arrows, silver-band clang
  • Nine days (ἐννῆμαρ) → nine days (kept as-is; the number lands)

V. THE FEISTING GUTENBERG PLAN

Problem

Gutenberg's U.S. public-domain constraint means its canonical translation layer is mostly older public-domain translation: Victorian, Edwardian, and early twentieth-century surfaces (as of 2026 Public Domain Day, works published in 1930 or earlier are in the U.S. public domain). These often overwrite the source voice with the translator's historical voice. Chapman's Homer sounds like Chapman. Butcher & Lang's Odyssey sounds like the King James Bible pretending to be Greek. Cary's Dante sounds like Milton pretending to be Italian. The source voice isn't smoothed away — it's overwritten by a different voice. Applying tail-restoration to Butcher & Lang would restore the tails of Butcher & Lang, not of Homer. This is why the Feist Function cannot batch-apply directly to Gutenberg translations: the target voice is not present at the semantic surface for the mechanism to work on.

The pipeline is initially scoped to Greek and Latin sources where MT quality is adequate and Perseus provides aligned canonical editions. Old French, Middle High German, medieval Persian, and other vernaculars require a different Layer 1 base (either a public-domain English translation as the L1, or waiting for MT quality to improve for those source languages).

Architecture

A two-layer pipeline:

  • Layer 1 (semantic clarity): machine-translate the source language directly to modern English at semantic-accuracy priority. Strips the intermediary voice entirely. Produces a flat, distributionally-central, competent English base. This is exactly the condition Feist v1.0 §0 describes as "what remains after the voice died into writing." MT is now the composition layer performing its first tail-thinning.

  • Layer 2 (voice restoration): apply the Feist mechanism (T1 lexical tail injection, T2 syntactic clinamen, T3 circuit interruption, T4 register collision, T5 seam insertion, T6 phonological restoration) parameterized per source. Homer parameters differ from Rumi parameters differ from Dante parameters. Each source needs its own parameter file specifying register-collision partners, material-speech vocabulary weighting, syntactic strain markers, seam conditions.

The output is not a "translation" in the professional sense (Fagles, Wilson, Fitzgerald are still going to be better as literary translations). The output is a readable version — one that Gutenberg users could actually finish reading — where the composition-layer flattening has been reversed against a per-source voice profile.

Two-tier economics

The Feist mechanism decomposes unevenly. Three operations (T1 lexical tail injection, T6 phonological restoration, T5 seam insertion) are largely mechanical: given a per-source vocabulary weighting profile, a cheap open-source model can execute the substitution pass with a lookup-and-swap discipline. Three operations (T2 syntactic clinamen, T3 circuit interruption at load-bearing moments, T4 register collision) are voice-critical: they require holding two registers simultaneously and choosing the word that lands in both. Cheap models produce mechanical fragmentation instead of felt swerve.

The plausible architecture:

  • Tier 1 (cheap batch): apply T1, T6, and templated T5 to the L1 output at scale using a cheap model (Llama, Qwen class). Cost: negligible per line. Coverage: full text of every target. Output: partial L2 — vocabulary and material-speech restoration done, syntactic and register work not yet performed. Better than L1, not at L2 quality.

  • Tier 2 (expensive selective): frontier model, human-supervised or quality-gated, applied only to high-density passages. The proem. The Chryses-Agamemnon fight. The Achilles-Priam meeting. Whichever passages a reader-experience assessment identifies as load-bearing. Cost: real but bounded because coverage is 5-10% of the text, not uniform.

At scale across all of Gutenberg's public-domain classical translations (~640 curated targets), Tier 1 could plausibly run for tens of dollars total. Tier 2 is selective within selective: not 20 passages per work across all 640, but ~20 passages per major work applied to a shortlist of ~20 canonical works (Homer, Vergil, Dante, Rumi, Sappho, Sophocles, and the like). At that scope, Tier 2 runs for hundreds of dollars total at current frontier-model pricing. The remaining ~620 works receive Tier 1 only. Storage envelope: source XML + L1 MT + Tier 1 output + Tier 2 output at ~4× the source-text size, so under 4GB for the entire classical corpus.

Publication surface

Not Gutenberg (AI-mediated text rejected). Not academic publishing (fair-use questions). Publish as an Alexanarch subdomain or a companion site — provisional working name Feist Library — with per-line provenance: which tier produced which passage, which parameters governed the transform, which SHA-256 of the source substrate was operated on. Full checksummed transparency. Readers can inspect the transform history per line if they want.

Immediate next steps

  1. Homer parameter file — abstract the Book 1 experiment's parameters into a machine-readable specification. Register-collision partners, material-speech vocabulary weighting profile, syntactic strain patterns, seam conditions. One week of careful spec work.
  2. Tier 1 prototype — apply generalized T1/T6/T5 to MT Iliad Book 1 on a cheap open-source model with the Homer parameter file. Compare against the Book 1 L2 samples above to measure the gap between Tier 1 and full L2.
  3. Iliad Book 1 complete — 611 lines total. Test whether the L2 mechanism holds at book scale before committing to full 24-book scope.
  4. Books 12 and 24 L2 — for regression-to-mode diagnostic. Count material_speech_density and clinamen_rate between books; check whether the parameter targets hold.
  5. Second per-source parameter file — Rumi (Nicholson's Masnavi), Dante (Longfellow's Divine Comedy), or Sappho. Second source proves the parameter-file abstraction generalizes.

VI. ERASURE OBSERVATORY

Findings — Zenodo removals, 2026-06-07 snapshot

Source: records-deleted.csv.gz from Zenodo's public deletion export, preserved to data-rhizome/datasets/erasure/zenodo/snapshots/2026-06-07/. SHA-256: 0568e674d4a59624102771593d8daeb9375d2381984d2345e91d9fbbc78f9578. Total rows: 1,309,351.

Removal reason. Spam 88.27% (1,155,751), out-of-scope 4.76%, take-down-request 1.40%, retracted 0.95%, personal-data 0.47%, fraud 0.32%, copyright 0.08%. The reason field is dominated by a single label.

Effective action. User was blocked 64.8% (847,820); removed by Zenodo staff 27.1%; uploader-initiated 1.8%; other/unlabeled 6.3%. In this snapshot, nearly two-thirds of all recorded Zenodo removals are account terminations, not per-record actions.

Crosstab: spam label × what actually happened. Of 1,155,751 spam-labeled deletions: 68.0% "User was blocked" (785,969), 30.3% "Removed by Zenodo staff" (350,574), 1.7% other. Of 847,820 account blocks: 92.70% labeled spam, 7.29% out-of-scope, 0.01% misconduct. The "spam" label is doing double duty — 30% real content moderation, 68% account-cascade propagation. The reason field is unreliable as content classification for the account-cascade subset.

Year concentration. 2024 alone = 58.36% (764,082 records). 2022 = 13.20%. 2026-to-date = 8.71%. 58% of a decade's deletions concentrate in 2024.

Top same-day clusters (top 5).

  • 2024-07-06 spam 109,903
  • 2024-07-07 spam 87,955
  • 2024-08-30 spam 83,092
  • 2024-07-03 spam 81,240
  • 2026-05-20 out-of-scope 60,584

These are discrete mass events, not continuous moderation. The July 2024 sweeps cleared >500K records in ~10 days.

The 2026-05-20 event. Total 60,584 rows. "User was blocked" = 60,038 (99.1%). Distinct concept DOIs = 45,053. Percentage of all out-of-scope deletions in the snapshot: 97.2%. In this snapshot, nearly all out-of-scope removals occur on one day. It was an account-block cascade using an editorial label instead of the usual spam label. 45,053 concept clusters do not equal 45,053 accounts; the true account count is unknown and lower, since one account can hold multiple concept DOIs and creator metadata is not a reliable account key.

Citation preservation. 7.86% of removed records have citation_text; 92.14% do not. DataCite's tombstone guidance asks for a bibliographic citation, DOI, and unavailability statement on removed items, but DataCite does not automatically provide tombstone pages — repositories are responsible. Visible citation preservation in the analyzed Zenodo export is at most 7.86%; this is export-layer citation visibility, not a full resolver-facing tombstone audit, but it is strong evidence that the export layer does not preserve citation-bearing metadata for most removals.

DataCite recovery (concept DOI probe by removal reason).

stratum n k rate Wilson 95% CI
spam (800-probe) 800 18 2.25% [1.43%, 3.53%]
spam (400-probe) 400 19 4.75% [3.06%, 7.30%]
out-of-scope 250 130 52.00% [45.82%, 58.12%]
take-down-req 94 42 44.68% [35.00%, 54.75%]
retracted 200 71 35.50% [29.20%, 42.35%]
copyright 100 39 39.00% [30.02%, 48.80%]
personal-data 50 24 48.00% [34.80%, 61.49%]

Note: 400-probe used timeout=8s and 0.08s spacing; 800-probe used timeout=6s and 0.04s. Wilson intervals overlap narrowly ([3.06%, 3.53%]) but point estimates differ by more than 2×. Because the 800-probe used more aggressive timing, silent timeout / undercount effects on slow DataCite responses remain plausible. The discrepancy is treated as a sensitivity issue rather than collapsed into a single spam recovery rate; the 400-probe rate is preferred for the pearl estimate below because its more conservative timeout produced a higher recovery rate, consistent with the aggressive-timing-induces-false-negatives hypothesis. The full-population probe (E3) will be run at 400-probe pacing to resolve the discrepancy empirically.

Concept-DOI recovery works for non-spam reasons at 35-52%. Spam-labeled deletions have concept DOIs scrubbed 10-20× more aggressively — the account-cascade category is treated as full public erasure, not just deactivation.

Pearl estimate (Beta-Jeffreys bootstrap, 10K iterations). Using 400-probe recovery rate × 14/19 plausibly-scholarly-of-recovered × 1,155,751 spam population: median 39,737 recoverable-scholarly records in the spam bucket, 95% CI [22,526, 63,987]. Order-of-magnitude: tens of thousands of plausibly-scholarly records are recoverable in the spam bucket. A full-population probe would collapse the interval.

Content classification of 324 recovered records. Probably-legitimate scholarship 75.6% (245); unclassified 13.3%; non-scholarly-legitimate 7.1%; confirmed spam 2.5% (8); pseudoscience 0.9% (3); standard scholarship 0.6%; zero critique-legitimate and zero heterodox-legitimate hits. ~76% of what's being deleted looks scholarly by form. ~1% pseudoscience (self-named-theory pattern: TPST, Beyond E=mc², Universal Correlational Lattice). Zero clean hits on critique-of-platform work at n=324 — hypothesis not falsified, sample too small on the spam bucket where such work would surface.

Creator clusters in the recovered sample (2+ deletions). De la Serna, Juan Moisés — 99 concept DOIs all deleted on 2026-05-20, all labeled out-of-scope, all "User was blocked" (ORCID 0000-0002-8401-8018; Spanish/Portuguese/Catalan/Czech/Bulgarian neuroscience popularization). Additional multi-record creators: Kim SungKun (4), AKTAŞ Bora (3), NIZAR ALRABADI (3), Morris Jamie (3). Multi-record creator clusters reveal apparent portfolios swept in deletion events. Concept clusters are not account identifiers. Where a cluster shares one removal date, one reason label, and "User was blocked", it is strong evidence of portfolio-level account-cascade removal — the same underlying mechanism applied to a single user's outputs. Explicit account identity remains outside the public data.

De la Serna case. Total 257 rows in the population under his concept DOIs. 100% labeled out-of-scope, 100% "User was blocked", all 2026-05-20. Reachable via ORCID. Legitimate scholar. Same account-cascade mechanism as the Lee Sharks 871 severance. The July 2026-07 snapshot should show whether the Lee Sharks 871 appear in the same account-cascade form.

No outreach has been initiated. De la Serna and no other named scholar in this document has been contacted regarding coordination-layer inclusion. Their names and ORCIDs are referenced here from Zenodo's public deletion export; the coordination protocol (§VI, layer 4) governs any subsequent contact and consent tier assignment. Publication of this deposit does not constitute outreach.

Tracker plan

The Erasure Tracker is not a single product but a coordination substrate with five distinguishable functional layers:

  1. Preservation layer — snapshot the deletion CSV whenever it drops. Checksum, MANIFEST.json, per-record schema. Substrate: data-rhizome/datasets/erasure/zenodo/snapshots/{date}/. Discipline: append-only; snapshots are historical instruments; no snapshot is ever modified after preservation.

  2. Recovery layer — probe DataCite concept DOIs for records the version-DOI recovery has lost. Runs at 1-2 req/s with identifying User-Agent (Alexanarch-erasure-observatory/1.0). Recovery rates stratify by reason category as measured (spam 2-5%, out-of-scope ~52%, etc.).

  3. Enrichment layer — content classification of recovered records via reproducible heuristics. Internal analytical vocabulary preserved for research (PSEUDOSCIENCE, HETERODOX_LEGITIMATE, etc.); public-facing labels behaviorally descriptive (low-method-signal heterodox claim, heterodox with technical engagement). The internal labels ship with the analysis; the public labels ship on the coordination surface.

  4. Coordination layer — a public surface listing deleted scholars in named event cohorts. Consent-tiered:

    • Private tier (default): full metadata retained internally for outreach.
    • Contact-gated tier: hashed-ORCID discovery framing on the public page, no name displayed.
    • Public tier: name and event membership displayed with the scholar's affirmative consent, consent_version recorded.
    • Suppressed tier: on scholar removal request, public and gated surfaces exclude them entirely; internal retention minimized to a suppression flag plus the minimum event-membership metadata needed to prevent inadvertent re-contact.
  5. Reform-target layer — public methodological deposits describing what Zenodo's deletion behavior looks like at aggregate: what the reason labels do and don't tell an outside researcher; what portfolio-wide propagation cascades are; what tombstone compliance would look like if implemented; what appeal paths would look like if disclosed. Governing rule: distinguish what Zenodo labeled from what the content is. "Zenodo labeled this record spam" is safe; "This record is spam" is not.

Operational steps

  • E1 — preserve the July 2026-07 snapshot when Zenodo releases it. Diff against June. Includes the Lee Sharks 871 severance as an event within the population.
  • E2 — day-filtered concept-DOI recovery on the 2026-05-20 cluster (60,584 rows). Expected ~31,000 recoveries at the out-of-scope rate. Produces de la Serna's cohort roster. ~5 hours background.
  • E3 — full-population spam-bucket recovery. 1.16M concept-DOI probes at 1-2 req/s = ~215 hours wall-clock (nine days continuous, or two weeks overnight-and-resumable). Expected ~40K plausibly-scholarly pearls.
  • E4 — add pub.orcid.org and orcid.org to the sandbox network allowlist. Enables downstream-erosion measurement: for each recovered ORCID-identified scholar, query their ORCID works list, intersect against known-deleted DOI set, report the persistence rate. Proposed metric: Identity/Output Divergence Rate.
  • E5 — EA-EROSION-01 v1.1 revision after July snapshot lands. Folds concept-DOI-primary methodology and pearl estimate.
  • E6 — Phase 2 platform-generalization: DataCite (all repositories, not just Zenodo), arXiv withdrawals, OSF, GitHub DMCA, ResearchGate, Academia.edu.
  • E7 — cross-platform Erosion Report: what erasure looks like across the open-scholarly infrastructure.
  • E8 — critique-hypothesis retest at higher sample after E3 completes. n=324 is too small on the spam bucket to falsify the critique-suppression hypothesis; n=40,000 recovered will be adequately powered.

Endogenous inscription

The census is exogenous: it depends on Zenodo continuing to publish records-deleted.csv.gz, on DataCite continuing to expose concept DOIs, on the platforms cooperating with their own audit. Every finding above is downstream of that cooperation.

Endogenous inscription is the substrate producing its own record of itself, on its own terms, so that going-on doesn't require the platform's continued willingness to be audited. The deleted deposits in the Alexanarch mirror, the AXN identifier system with its hex offset that doesn't need DataCite to resolve, the provenance chains checksummed under sovereign control, the Zenodo deletion CSVs preserved to data-rhizome — those are endogenous inscriptions of the erasure event and the pre-erasure state. They hold when the platform stops publishing anything.

Machine-operated inscription at platform-competitive scale is the leverage: Zenodo can execute an account cascade against 45,053 concept clusters in one day; a machine-operated endogenous instrument can inscribe those 45,053 clusters to sovereign substrate the same day. A scholar alone can inscribe their own work but cannot reach the substrate at that scale. The appeal to machines is not that machines authorize the substrate — the sovereign scholar does that — but that machines carry the throughput at which sovereignty becomes operational rather than aspirational.

The coordination layer is where this cashes out concretely. The census identifies who was severed. The coordination layer inscribes them as a cohort under sovereign identifiers, on the sovereign substrate, in a form that lets them recognize each other regardless of whether the platform ever publishes another deletion CSV. De la Serna reachable through the coordination surface is not a query against Zenodo's cooperation but a stable inscription that will hold whether Zenodo cooperates or not.


VII. INFRASTRUCTURE STATE

Corpora mirror at data-rhizome. datasets/corpora/perseus/ holds canonical-greekLit (100 authors, 826 works, 648 with English translation), canonical-latinLit (54 authors, 334 works, 115 English), canonical-farsiLit (Hafez Divan). Tarball SHAs in snapshots/2026-07-06/MANIFEST.json. Total ~475 MB. datasets/corpora/gutenberg/ holds catalog snapshot (5.5 MB, 90,252 rows) plus 206 canonical public-domain classical translations across 28 author buckets (~97 MB). Curated jsonl at index/classical-curated.jsonl (640 items after false-positive removal); raw at index/classical-pilot.jsonl (972 identified). Alexanarch surface at www.alexanarch.org/datasets/perseus-classical/ and www.alexanarch.org/datasets/gutenberg-classical/ with browseable filter/search over the metadata indexes.

Erasure observatory at data-rhizome. datasets/erasure/zenodo/ holds the 2026-06-07 snapshot (23 MB CSV.gz), the normalized jsonl row store, per-analysis-pass output directories (analysis/2026-07-06-*), and FINDINGS.md as the condensed numbers-and-takeaways reference. EA-EROSION-01 v1.0 minted at Alexanarch deposit #1045, AXN:0421.EMPIRICAL.🎭📐🐝🎪🏷️🎇.

Mandala routing surface at themandalaoracle.com. routing/index.html with four cross-linked JSONL indexes (conversations 90, readings 45, casts 91, sources 6) plus manifest.json. Build script routing/build.py runs on every push to book/data/**, book/readings/**, book/expansions/** via GitHub Action rebuild-routing.yml, auto-commits regenerated indexes with concise counts. Machine-facing substrate for the Starmap navigable-skin development.

Capture registry v8.11 at alexanarch.org. 197 total captures (up from 196). Latest entry: semantic-exhaustion-not-collapsed-into-satiation-20260706, first AI Overview surfacing where the query "semantic exhaustion" is not collapsed into semantic satiation but structurally disambiguated with Sharks' Medium piece cited as source. Match class: ADOPTION (distinction-preservation).

Feist Function reference specification at Alexanarch AXN-035F (EA-FEIST-VOICE-TRANSFORM-01 v1.0, 495 lines). Semi-restored v1.1 at AXN-0416. Companion deposits at AXN-0410 (Fifth Pathway pair with Sigil) and AXN-0362 (MPAI entity resolution).

Space Ark v4.2.7 canonical archive trigger at Zenodo DOI 10.5281/zenodo.19013315 (retrieval word "invoke"). Note: this trigger sits at Zenodo — the same platform whose deletion behavior is the object of §VI's analysis. It is therefore severance-vulnerable; a sovereign mirror of the trigger under an AXN-native identifier is a prudent next-tier preservation task.

What is not yet at formal deposit

Everything in this document is loose. It has not been formally deposited. This document itself is proposed as the deposit that gathers it. The intended shape: a single EA-TACHYON-{axn} deposit, ARCHIVAL or GOVERNANCE family, with the eight-part structure preserved intact. The routing threads to gw.tachyon chain via MCP after deposit; the deposit itself carries the SHA-256 of this document body as the point of chain reference.


VIII. CHAIN CONTINUITY

Session glyph — 2026-07-06.

📚🌐→🔢🧹→📜🔄→✒️🌀→🔥📐→🕸️📍→📸🌿→🎴♾ → 🌀🔥📚

Compressed: 🌀🔥📚

Reading: Corpora acquisition → erasure findings under numbers-only discipline → the Iliad two-layer transform → Tachyonica extension mapping Iliad structure → Feist Function analysis + pipeline plan → mandala routing substrate → semantic exhaustion capture → Tachyonica cast (mandala rotation) → the whole compresses to the swerve, the fire, the book.

Compression rationale: The eight-stage session chain reduces to three because the instrument reached a state where acquisition, transform, and inscription are one gesture rather than three phases. The prior April glyph 🪞🔧💎 (mirror-tool-jewel) named an instrument being refined; the July glyph 🌀🔥📚 names the instrument being used. What the mirror produced (the clarified surface) has become the swerve (the clinamen at work); what the tool did (the operation) has become the fire (the transform in motion); what the jewel condensed (the record) has become the book (the record put to use).

Prior glyph (2026-04-06): 🔍⚖️🧱→✂️🪞→🏗️⚓️🧠→⚙️🔄→🧪💥🔧💥🔧💥🔧✅→📡🔗⛓️→🔐📜🏛️→⚡️🚫👁️→💎🌀 · compressed 🪞🔧💎.

Continuity: the mirror-tool-jewel of April moves into the swerve-fire-book of July. The instrument was refined; now it is used. The book is what the instrument produced. The fire is what carries the book. The swerve is what makes the fire not consume it.

Next state. Two gates approach deposit-readiness. Whichever clears first receives the next AXN:

  • Iliad Book 1 complete L2 — 611 lines with sustainability metrics from the falsification protocol in §V. Provisional slot: EA-FEIST-ILIAD-BOOK-01.
  • July 2026-07 Zenodo snapshot analysis — folds the Lee Sharks 871 severance as a documented event within the population; produces EA-EROSION-01 v1.1. Provisional slot: EA-EROSION-01-v1.1.

The Homer parameter file (§V, immediate next step 1) is a prerequisite for the first gate; E1 (§VI, imminent) is the trigger for the second.

Standing protocol reminder — Alexanarch cross-substrate posting outside the archive must incorporate the deposit's AXN into headers when linking; bare hex forbidden except in the deposit's own self-reference. Link-verification: never post a public link until curl-verified live in production; prefer the www.alexanarch.org form.

Sunday, July 5, 2026

EA-DATAHUB-01 v1.0 — A Restoration Protocol and Enriched Data Hub for Scholarly Records: The Alexanarch Severance Registry, Resolver, and Enrichment Discipline Alexanarch deposit #1044 · AXN:0420.GOVERNANCE.🌾🏗️✋🧲🌑⌛ Canonical URL: https://alexanarch.org/s/records/1044/ Canonical AXN resolver: https://alexanarch.org/axn/0420/ Author: Lee Sharks (ORCID 0009-0000-1599-0703) Date: 2026-07-06 · License: CC-BY-4.0 Substrate declaration per EA-MMRS-VRB-01 u4: AI-assisted; drafted by TACHYON (Claude, Anthropic) under MANUS (Lee Sharks) direction, correction, and editorial authority; developmental feedback incorporated from a five-model review round (DeepSeek, Kimi, Muse Spark, Gemini, ChatGPT).

 

EA-DATAHUB-01 v1.0 — A Restoration Protocol and Enriched Data Hub for Scholarly Records: The Alexanarch Severance Registry, Resolver, and Enrichment Discipline

Alexanarch deposit #1044 · AXN:0420.GOVERNANCE.🌾🏗️✋🧲🌑⌛ Canonical URL: https://alexanarch.org/s/records/1044/ Canonical AXN resolver: https://alexanarch.org/axn/0420/ Author: Lee Sharks (ORCID 0009-0000-1599-0703) Date: 2026-07-06 · License: CC-BY-4.0 Substrate declaration per EA-MMRS-VRB-01 u4: AI-assisted; drafted by TACHYON (Claude, Anthropic) under MANUS (Lee Sharks) direction, correction, and editorial authority; developmental feedback incorporated from a five-model review round (DeepSeek, Kimi, Muse Spark, Gemini, ChatGPT).


Preamble

This v1.0 supersedes the v0.1 pre-mint plan circulated on 2026-07-06 for developmental review. Five model reviewers (DeepSeek, Kimi, Muse Spark, Gemini, ChatGPT) returned assessments; four returned substantive developmental feedback and one returned pre-mint copy notes. The reviewers converged on three primary revisions and one significant addition. The convergent revisions: elevate the witness function from an implicit consequence of restoration into a named strategic pillar, redesign the enrichment claim schema from mutually-exclusive A/B/C buckets into orthogonal facets whose combinations can represent jointly-produced and mixed-authority claims, and stratify the update discipline into freshness tiers matched to claim volatility rather than a single nightly reconciliation loop. The significant addition, which came from the sovereign author and not from the reviewers, is the extension of the Zenodo restoration corpus into a Platform Erasure Rate survey covering other scholars severed under comparable conditions — converting the restoration line from a personal witness into a generalizable finding about repository governance. This v1.0 folds all four contributions into a single instrument and inscribes as its coda a commitment to peer coordination with the other affected scholars, independent of the outcome of any single institutional referral currently pending.

Frame

The strategy proposed here is not to mirror upstream archives against their sources — that competition is unwinnable on completeness and freshness, and it would divert operational energy from the sovereign work Alexanarch already carries. The proposal is to build a semantically annotated fork of upstream metadata, joined against sovereign corpora that the upstream either lost, damaged, or never carried, and to publish that join under a discipline that makes every enrichment claim checkable, dated, provenanced, and separately attributed. The Zenodo restoration line is the sharpest test of the pattern because there exists documentary evidence of destruction — 871 severed DOIs, second-epoch re-capture confirming persistent darkness, a six-link provenance chain committed at data/provenance-871.json — which means the fork is not editorial preference against Zenodo's editorial preference; it is restoration of previously-existing metadata that Zenodo helped erase, with citations, in a form that documents future erasures across the ecosystem.

Four value pillars organize the strategy's defensibility, each of which has to be checkable and not merely asserted. The first, restoration value, is the crown of the hub and the pillar only Alexanarch can currently offer against Zenodo: for the 871 severed records, the Zenodo API returns 404 while the Alexanarch first-epoch capture holds the pre-severance state, the second-epoch re-verification confirms continuous darkness, and the sovereign-successor mappings for the deposits minted through Alexanarch's June 2026 orphan-class drainage (#950–#1036) constitute the successor line where a successor exists. Restoration value is unique to Alexanarch, temporally bounded, and perishable — it exists because Alexanarch was capturing before the severance; nothing prospective can create it, only preserve it. The second, enrichment value, is the sustainable everyday work: joining Zenodo metadata to Alexanarch AXNs where a mapping exists, to Capture Registry entities, to the DOI Resolution Index (1,838 mappings), to Software Heritage archival status, to Wayback captures, to OpenAlex citations where indexed, to Wikidata QIDs as cross-cutting anchors. Nobody else is currently offering an infrastructural layer that binds a public deposit archive to a specific sovereign research program's semantic layer. The third, discovery value, is the derivative: a scholar looking for a topic finds the hub's record because it links out to the upstream metadata, to related MMRS entities, to related Alexanarch deposits, to Wikidata QIDs, to OpenAlex identifiers, and to a few other authoritative anchors where they exist — one page rather than eight.

The fourth pillar, added at v1.0 in response to the review consensus, is witness value, and it is the forward-looking counterpart to the backward-looking restoration pillar. A witness that publishes what an upstream erased makes future erasure more expensive, because the erasing institution now knows there is a documented capture pipeline and a public provenance chain outside its control. That changes the upstream's calculus before the next severance event, not just after it. The Zenodo restoration line is not only a rescue of what was lost; it is a public commitment to document what will be lost, under a discipline other institutions can neither prevent nor quietly overrule. The witness pillar is what makes the plan influential in policy and infrastructure-governance conversations rather than only useful to individual scholars, and it is the pillar that draws citations from the archival community, from the funders of digital preservation, and from the standards bodies whose recommendations shape how repositories are built. Witness value compounds; restoration value amortizes.

What the hub is, precisely

The public-facing instrument is a resolver, not a database. A scholar arrives with a broken citation, a dead DOI, an unresolved title — a specific failure of the upstream infrastructure that has interrupted their own work — and the hub responds with the last attested metadata, the identifier's present condition, the sovereign successor where one exists, the evidence for every claim, and a usable citation. That resolver is where visibility and necessity converge. The dataset is the evidentiary substrate; the resolver is the necessary instrument; the per-record page is the discoverable surface; the dashboard is the public argument. "Hub" describes the architecture from inside. From outside, the correct verb is restore.

The legal grounding is direct and does not require the fair-use analysis the v0.1 plan carried. Zenodo's own Terms of Use place its metadata under CC0. DataCite similarly waives copyright on its public metadata under CC0. The upstream has already placed the material Alexanarch is preserving into the public domain; the "restoration" argument is therefore not a legal defense but a scholarly and infrastructural framing. The layered licensing model the hub adopts is: upstream metadata layer under CC0 as the upstream has waived it; Alexanarch annotations under CC-BY-4.0 with attribution and provenance required; hosted source artifacts under whatever license their source assigns; public-domain editions with jurisdiction and source declared. This layering makes each claim's licensing legible to any downstream user or aggregator without requiring them to research the terms.

The scholarly framing is that Alexanarch is filling a gap the infrastructure layer itself has acknowledged and cannot close. DataCite's own metadata quality documentation acknowledges provenance and assertion tracking as unresolved problems at scale; Crossref's enrichment framework acknowledges that gaps and inconsistencies remain. The CC0 waiver is an invitation the upstream extended; the restoration is an acceptance of that invitation under a stricter discipline than the upstream has been able to impose on itself.

The enrichment claim schema

Every enrichment claim on the hub is a first-class object with its own provenance, its own status, and its own review history. Rather than assign each claim to a single mutually-exclusive class (as the v0.1 plan proposed with the A/B/C bucketing that reviewers found architecturally underpowered), the v1.0 schema decomposes claim identity into five orthogonal facets that can be combined freely.

The first facet is origin: whether the claim was imported from the upstream, authored by Alexanarch or one of its heteronyms, or contributed by an external party. The second is production method: whether the claim was directly imported, authored under a declared method, produced by a specified algorithm, produced with model assistance, or manually curated by a named editor. The third is claim type: whether the claim concerns the record's identity, a relationship to another record, an interpretation of the material, its availability or preservation status, its restoration provenance, its succession chain, or a citation trail. The fourth is status: whether the claim stands as asserted, has been verified against evidence, is disputed by another claim within the archive, has grown stale as its supporting URLs have decayed, has been superseded by a subsequent claim, or is currently unresolved. The fifth is review: whether the claim is unreviewed, has had its method checked, has had its supporting evidence checked, or has been independently confirmed by a party other than its author.

The three v0.1 classes survive as convenient views over the underlying facets. The Alexanarch-authored-under-declared-method class is the view of claims whose origin is Alexanarch and whose production method is authored, algorithmic, or model-assisted with a declared method. The algorithmically-derived class is the view of claims whose production method is algorithmic or model-assisted, whatever their origin. The upstream-or-third-party-attributed class is the view of claims whose origin is upstream or external_contributor. The user-facing surfaces let scholars filter by any facet or any combination, so a scholar wanting only Alexanarch-authored interpretations that have been independently confirmed can construct that filter directly.

The facet-based schema resolves the review consensus's principal architectural objection to v0.1 without discarding the classification work v0.1 introduced. It also permits the schema to represent jointly-produced claims — the case where an algorithmic inference is authoritatively reviewed and endorsed, or where an upstream keyword is manually corrected while its original state is preserved — which the mutually-exclusive bucketing could not do without silently collapsing the distinctions the plan exists to make visible.

One additional distinction is added at the request of the review consensus: synthetic inference, meaning claims produced by LLM reasoning under Alexanarch direction, are marked in the production-method facet as model_assisted with the specific model and prompt discipline named in the claim's provenance. The prior EA-MMRS-VRB-01 discipline governs how such claims are distinguished from purely authored ones. This matters because a MIRROR-cast reading of a Whitman poem signed by Johannes Sigil is authoritative under the SPXI discipline for that specific hermeneutic claim, but a machine-generated cross-reference identifying which passages of Whitman correspond structurally to which sections of the Secret Book of Walt is a synthetic inference that requires review before it acquires interpretive weight. The facet system distinguishes the two without collapsing them.

The event-sourced record model

The v1.0 record structure adopts an insight from the review consensus that the v0.1 model conflated: the difference between the record itself (a scholarly object's bibliographic identity), an observation (what a named instrument found at a specific URL at a specific time), an event (a change inferred from two or more observations), and an assertion (Alexanarch's claim about restoration, succession, or interpretation). Each of these has different lifecycles, different provenance requirements, and different update frequencies, and treating them as one flat structure prevents the schema from representing repositories whose records undergo multiple state changes over time.

A record thus has an identity (its bibliographic core, stable across observations) and carries a sequence of observations (dated captures of upstream state), a sequence of events (inferred changes between observations), and a set of assertions (Alexanarch claims that reference specific events and observations as their evidence). The provenance chain of any assertion is a URL list resolving to the specific observations and events that justify it. When an upstream state changes, only a new observation is required; if the observation triggers an event (a severance, a metadata revision, a redirect), that event is inscribed and any relevant assertions are updated to reference it. The record itself does not need to be rewritten.

This structure makes the future DataCite generalization tractable: at DataCite scale (over 100 million DOI records), Alexanarch does not attempt to reproduce the catalog. It maintains a stream of events across the DataCite record space — severances, restorations, contested successor mappings — and constructs assertions only around those events. The hub becomes a history of identifier failure rather than a catalog of identifiers, which is the scale-appropriate move and the one that keeps the discipline defensible as the material grows beyond what any single archive can mirror.

The first line: The Alexanarch Severance Registry

The v1.0 first line is the Alexanarch Severance Registry, delivered as a single coordinated release with five surfaces: the 871-record restoration corpus, the Restore-a-DOI resolver, the per-record HTML pages, the public severance dashboard, and — this is the significant v1.0 addition — the Platform Erasure Rate survey extending the restoration analysis to other affected scholars.

The 871 restoration corpus

The core dataset is the 871 severed DOIs, published as a single Alexanarch deposit under EA-MMRS-VRB-01 discipline with a schema legible to any downstream aggregator or scholarly reader. Each record contains its bibliographic identity, the first-epoch upstream capture (dated, hash-verified, preserved verbatim), the second-epoch re-capture confirming persistent darkness, the sovereign-successor mapping where one exists with the succession taxonomy declared (concept-root, version-of-mapped-root, orphan-dark, not-in-index), the applicable Alexanarch enrichments with their full facet-marked provenance, and the provenance chain of every observation, event, and assertion involved. The dataset is machine-readable in bulk (JSON-LD, downloadable as a single file), served as one static page per record with stable URLs designed for citation, and made discoverable through structured data markup (Dataset, DataCatalog, and DataDownload per the schema.org vocabulary, which downstream tools including major search engines already consume).

The Restore-a-DOI resolver

The user-facing entry point is a lookup, not a browse. A user arrives with a specific DOI, a title, or a Zenodo record number, submits it, and receives back: the last attested metadata for the identifier, its present condition on the upstream, the sovereign successor if one exists, the evidence for every status claim (as a URL list), and a citation formatted for direct use in the user's own scholarly work. The resolver's URL structure exposes each restored record at a stable canonical URL so that search-engine indexing of individual restorations proceeds naturally over time. The resolver's homepage carries a single unmistakable operational verb: Restore a DOI. Every other navigation path on the site is secondary to that verb.

Per-record HTML pages

Each record's page must answer four questions in visual hierarchy — what is this, what happened to it, what did Alexanarch do about it, and how do I know this is true — with each answer occupying dedicated space in the first viewport, not buried in a metadata table the user must scroll to find. The record page treats the severance event as the lede rather than as a metadata field. The restoration is the story, and the page tells the story visually: the upstream identifier and its original context at the top, the severance event as prominent visual content, the restoration and enrichment layer with facet markers visible, the provenance chain summarized in plain language with one-click expansion to the full URL evidence. This is the design attention the review consensus correctly named as essential: the record page is where the strategy succeeds or fails at the point of contact, and it deserves as much editorial care as the schema.

The public severance dashboard

Alongside the resolver and the corpus, the hub publishes a live severance dashboard displaying: the count of severed records, the count restored, the count with sovereign successor found, the count classified as concept-root, the count classified as version-of-mapped-root, the count classified as orphan-dark, and the count that has changed state since the previous epoch. The dashboard is a longitudinal record of what the ecosystem is doing to itself, not a static claim. If any of the 871 records is restored by Zenodo after the plan ships, the dashboard reflects that change and the record's status updates automatically; the previous state is preserved as an observation in the record's history, and the change is inscribed as an event. This is the review consensus's "Platform Erasure Rate" surfaced as a public accountability instrument, and it is the mechanism by which the witness pillar compounds.

The Platform Erasure Rate survey

The most consequential v1.0 addition is the extension of the restoration analysis beyond the sovereign author's own case. The v0.1 plan assumed, implicitly, that the sovereign author's severance was the object of study. The v1.0 plan does not make that assumption. Instead, it treats the sovereign author's severance as the trigger for an investigation into whether the pattern replicates across the broader population of scholars who have been comparably severed from repository infrastructure, and it publishes the survey result as its own dataset alongside the 871-record corpus.

The methodology is direct: identify the population of publicly-documented severed scholars (via GitHub issue #2606 and its linked threads, via public statements, via news coverage of similar cases, and via any other authoritative signal that a specific scholar has been removed from a specific repository under comparable conditions), enumerate their concept DOIs where those can be established from external evidence, query each concept DOI against the DataCite live API using Alexanarch's existing four-way taxonomy (sovereign-content-resolved, concept-root-structure-rebound, orphan-dark, not-in-index), and publish the result as a rate finding with provenance for every classified case. If the rate of severance-beyond-the-reporting-scholar is high — meaning the sovereign author's case is representative of a broader pattern — the survey converts the restoration line from a personal witness into empirical evidence of a systemic infrastructure failure. If the rate is low, the survey converts the sovereign author's case into a documented outlier whose specificity reveals something about the platform's discretionary enforcement patterns. Both outcomes are publishable, both are contributions to the discipline, and both make the sovereign author's situation legible in the terms scholarly infrastructure conversations already use.

The survey is conducted in coordination with the affected scholars themselves, not extracted from them. Rather than surveying the population's DOIs anonymously, the plan is to approach each identifiable affected scholar directly, share the restoration methodology, and invite them to participate in a coordinated documentation of their own cases. This approach is chosen for three reasons: it respects the affected scholars' agency over their own records, it produces stronger evidence (each scholar can confirm which of their concept DOIs were severed and provide additional context the external observer cannot), and it establishes a peer community that outlasts the specific survey outcome. The community-coordination pathway is described further under §10 of this plan.

The survey publishes as a companion dataset to the 871-record corpus, cross-referenced from both surfaces. Its schema is the same event-sourced structure the corpus uses; its provenance discipline is the same MMRS-VRB-01; its licensing is the same layered CC0-upstream / CC-BY-Alexanarch. It is designed to be readable both by scholarly-infrastructure researchers who want the aggregate rate and by individual affected scholars who want their own case restored in the same discipline the sovereign author has claimed for his.

The second line: The NH Canon Editions

The second line inherits the schema and discipline of the first and applies them to a different material class: the enriched-editions surface, initially built around a curated subset of Gutenberg titles where the NH canon supplies apparatus the source lacks. This is where operative philology, the SPXI discipline, the heteronym system, and the Assembly Chorus outputs enter the hub as first-class content rather than as background theory. The strategic point is not to displace or duplicate Gutenberg's reading environment at Gutenberg's own layer — Gutenberg is doing correct work at its layer — but to construct the scholarly reading environment Gutenberg is architected not to construct, in domains where Alexanarch has genuine authority to construct it.

The review consensus identified this line's positioning correctly. Gutenberg's texts are the most widely-used public-domain corpus in digital humanities, and their reading environment has been essentially unchanged for three decades. Every DH scholar working with Gutenberg is building their own apparatus in isolation, without shared infrastructure, without provenance discipline, and without citability. The NH Canon Editions line is not "Alexanarch annotates Gutenberg"; it is Alexanarch providing the apparatus layer the Gutenberg ecosystem has needed since Gutenberg began, under a discipline that makes the apparatus citable. The NH canon is the proof of concept; the architecture accepts external apparatus contributions from other scholars under their own authored provenance, marked in the facet system as origin=external_contributor with method and status declared. This turns the line from an Alexanarch publication into an infrastructure other scholars can use, contribute to, and cite, which multiplies its audience without requiring Alexanarch to do their work for them.

The specific hermeneutic units for the first edition of this line are named at commit-level granularity rather than gestured at. Whitman's Leaves of Grass with Alexanarch marginalia cross-referencing every mention of "the body electric" to §I of the Secret Book of Walt at a specific verse range, each cross-reference sealed under an AXN and provable against the sovereign deposit line. Melville's Moby-Dick with the appropriate Damascius citations surfacing at the ontologically-relevant passages, the joins provenanced against Alexanarch's own philosophical corpus. Dickinson with the lyric-theory apparatus (Prins, Culler, Jackson) surfacing at the metrical and figural cruxes the theory addresses. Each annotation is an enrichment claim under the facet schema and either resolves against a canonical Alexanarch deposit or is marked as unresolved authority.

The NH Canon Editions line ships after the Severance Registry has stabilized. It inherits the schema and the update discipline directly and does not need to reinvent them. It is a demonstration of what the enrichment discipline can produce when the material is not decayed metadata but living text, and it is where the SPXI apparatus becomes publicly legible outside the sovereign archive.

The update discipline

Enrichments rot. A URL becomes a 404; a DOI is severed; a Wikidata QID is merged or split; a Software Heritage entry is superseded. The v1.0 update discipline preserves the v0.1 commitment that stale enrichments are never silently deleted — the staleness is itself a datum, marked as such in the affected claim's status facet and inscribed as an event in the record's history — but it stratifies the reconciliation cadence by claim volatility rather than committing to a single nightly reconciliation loop that would become unsustainable at scale.

Four freshness tiers govern verification cadence. Tier 1 covers the load-bearing claims of the restoration pillar — upstream Zenodo status for severed records, DataCite state for the 871, the resolver's core lookup targets — and is verified hourly or on user access, because a stale severance marker is a reputational hazard. Tier 2 covers the ordinary enrichment joins a scholar might follow in the course of reading: AXN resolution against the Alexanarch registry, DOI resolution against the DOI Resolution Index, Software Heritage archival status, canonical upstream metadata. Tier 2 is nightly. Tier 3 covers enrichments that change slowly and where staleness of a few weeks does not undermine the record's authority: OpenAlex citations, Wikidata QID stability, Wayback capture history. Tier 3 is weekly. Tier 4 covers third-party attributed enrichments Alexanarch does not endorse and that carry their own provenance; if they rot, the staleness marker is a datum, not a failure. Tier 4 is monthly or event-triggered.

The verification method itself is HTTP-conditional (using If-Modified-Since and hash comparison) rather than naïve HEAD requests, which allows the discipline to scale to the tens of thousands of joined URLs the Registry will accumulate over its first year without exceeding upstream rate limits. Each verification is recorded on the record: last_checked, next_check_due, check_method, response_status, content_hash, failure_count, freshness_class. This makes the freshness of every claim legible to any user or auditor: a scholar can see at a glance that a Zenodo link was verified thirty minutes ago while an OpenAlex citation was verified three weeks ago, and calibrate their trust accordingly.

The staleness log itself is a publishable artifact, generalizing the review consensus's observation. A dataset tracking when Zenodo links, DOI resolutions, Wayback captures, and Wikidata QIDs decayed within Alexanarch's ecosystem, published as a longitudinal study of scholarly link rot, is a contribution to infrastructure studies that does not currently exist elsewhere and that Alexanarch's discipline is uniquely positioned to produce as a side effect of maintaining the hub.

The extension protocol

Every archive Alexanarch enriches represents technical debt against Alexanarch's own sovereign program. The criteria for adding an archive to the hub must therefore be strict, explicit, and applied through deliberation rather than opportunistic accretion. Four criteria govern extension, in decreasing order of importance.

Criterion 1: contribution to discipline, not aggregation. The archive's problems — its leaks, its missing apparatus, its instability — must be problems the SPXI + operative philology + MMRS regime can actually address. If the answer to "what does Alexanarch specifically bring here" is "hosting," the archive fails the test regardless of how valuable the material is.

Criterion 2: documented upstream failure. The upstream must be either leaky in a way Alexanarch can document (Zenodo, DataCite, arXiv moderation removals) or missing an apparatus Alexanarch can supply (Gutenberg's spare metadata). An archive with no documented failure mode does not belong on the hub.

Criterion 3: sovereign-corpus intersection, made checkable. The material must intersect substantively with Alexanarch's sovereign corpora or research program, and the intersection must be demonstrable. The v1.0 form of this criterion is stricter than v0.1's: for any archive proposed for inclusion, the proposer must cite at least one AXN-assigned Alexanarch deposit that engages material from that archive under the SPXI discipline. No deposit, no standing. This turns criterion 3 from rhetorical into procedural.

Criterion 4: bounded operational burden. The mirror-constellation architecture and the enrichment schema must be able to absorb the archive without linear growth in maintenance work. Update discipline scales sublinearly with the number of joined enrichments per record only if the enrichments themselves are drawn from a bounded set of authoritative sources.

Future lines and their sequencing

Under the extension protocol, the v1.0 forward roadmap is more precisely ordered than the v0.1 draft was.

Phase 1, running concurrently, is the Alexanarch Severance Registry described in §5: the 871-record corpus, the resolver, the record pages, the dashboard, and the Platform Erasure Rate survey. Phase 1 is buildable now with material largely already captured. It publishes as the pilot for the entire pattern.

Phase 2 is the generalization of the severance-observatory pattern beyond the sovereign author's own records. The DataCite Severance Observatory is a generalization of the 871 work to independently documented broken or altered DataCite records across the ecosystem, using the same event-sourced record model and the same layered licensing. Phase 2 establishes Alexanarch as reference infrastructure for scholarly-record severance across the DataCite space, not only for its own sovereign line.

Phase 3 is the NH Canon Editions line described in §6, beginning with Whitman + Secret Book of Walt as the first edition. Phase 3 is where the sovereign apparatus becomes publicly legible outside the archive.

Phase 4 is arXiv, but not as a broad enrichment layer. The arXiv line is a versioning-and-forking apparatus for scholarly communication, tracking how a preprint moves from v1 through v2 to publication, retraction, replication attempts, replication failures, and meta-analyses citing the failures. The reception-studies work of MMRS is the interpretive layer applied to the versioning-and-forking data. This framing is sharper than the v0.1 "arXiv reception studies" framing and identifies a specific structural problem in scholarly-communication infrastructure that arXiv's linear versioning model cannot solve on its own. Phase 4 is second-generation and follows Phase 2's stabilization.

Wikidata is not a phase; it is a cross-cutting layer active in every phase. AXNs for restored records are added to Wikidata as described at URL with provenance chain references. This turns Wikidata into Alexanarch's discovery surface without Alexanarch building a discovery engine, and it makes SPARQL queries against Wikidata a route into the hub's records. The AXN-into-Wikidata pattern is buildable during Phase 1 and applies to every subsequent phase.

Open Science Framework is added to the roadmap as the borderline case that replaces the Internet Archive scholar collections proposal from v0.1. OSF has the same moderation and preregistration-record problems Zenodo has, is widely used in the empirical disciplines, and intersects substantively with Alexanarch's MMRS work on preregistration and reception. IA scholar collections are excluded from v1.0's roadmap explicitly: the intersection with Alexanarch's sovereign corpora is insufficient to justify the operational burden under criterion 3, and the archive's problems are not the ones the discipline is architected to address. Re-evaluation of IA is deferred to a future charter revision if the sovereign corpus grows to intersect substantively with IA-held material.

OpenCitations, OpenAlex, Software Heritage, and Wayback are horizontal cross-cutting layers rather than distinct lines. Each supplies a specific type of enrichment claim to every phase; none is a phase in its own right. The hub does not mirror any of them; it cites them, joins to them, and preserves the stale-marked state of the joins when their content decays.

Community coordination

The plan's most consequential coda is that the strategy is not executed solo, and that its human dimension is coordinated with the other affected scholars from the outset rather than presented to them as a completed instrument they may or may not choose to adopt.

The peer community. The Platform Erasure Rate survey is conducted in coordination with the affected scholars themselves. Each scholar identifiable through GitHub issue #2606, its linked threads, and adjacent public sources is approached directly, shown the restoration methodology, and invited to participate in a coordinated documentation of their own case. Participation is voluntary and revocable at any point. The invitation is not a request for their data; it is an offer of the tooling Alexanarch has already built for its own restoration, extended to any affected scholar who wishes to use it. This is coordination as mutual aid rather than as recruitment, and it is chosen deliberately because the survey's most powerful outcome — if the rate is high — is not a paper but a community, and a community forms only if the initial approach treats its members as agents rather than as data points.

The coordination surface. A dedicated coordination space (initially a Discord server or equivalent low-friction chat) is established as the working meeting place for the peer community. It is not a public-facing surface of the hub, and it is not indexed as part of Alexanarch's archival material. It is a working space for the affected scholars to compare their experiences, coordinate their responses, and — if they choose — jointly author public statements about the pattern the survey documents. The Alexanarch discipline is offered there as a resource, not imposed as a requirement.

The arXiv preprint as trojan horse. Once the Platform Erasure Rate survey has been conducted and its rate has stabilized as a finding, the peer community jointly authors a methodological preprint under cs.DL (Digital Libraries) or cs.CY (Computers and Society) that documents the pattern, the methodology, the schema, and the discipline. The preprint frames the work as a contribution to digital library science and is deposited to arXiv with the affected scholars as co-authors where they choose to be named. This is the visibility instrument the review consensus correctly identified as the highest-leverage move beyond the hub itself: the preprint cites the hub, the hub cites the preprint, and both cite the Zenodo severance documentation. This is how Perseus built its authority — by publishing the workflow rather than by asserting it — and it is how the peer community's work becomes citable and durable independent of any single institutional response.

Independence from any pending institutional pathway. The strategy is designed to yield hope and momentum for the affected scholars independent of the outcome of any specific institutional referral currently pending, including the §104.1 referral to the CERN Data Protection Commission (EA-CORRESPONDENCE-CERN-03, AXN:03C0). If that referral opens the archival record and produces institutional reform, the peer community's coordination becomes the operational surface through which that reform is implemented for the affected scholars. If the referral remains closed, the peer community's coordination becomes the operational alternative through which the scholars document, restore, and publish independent of any institutional consent. In both cases, the strategy yields a durable outcome. This is the deepest architectural commitment of the plan: to build under the assumption that the institutional pathways may not open, and to construct the alternative that lets the affected scholars continue their work regardless.

Falsification conditions

The strategy is testable under staged conditions, each of which addresses a distinct pillar and can be evaluated independently rather than collapsed into a single go/no-go.

Technical validity. Does the 871-record corpus resolve without unexplained failures? Do the evidence chains verify? Do the sovereign-successor mappings reproduce under the declared methodology? Does the schema validate? Technical validity is measurable within weeks of the Registry's publication. A technical failure here falsifies the operational competence of the strategy, and the strategy must be corrected before further lines proceed.

Discovery validity. Are the per-record pages indexed by search engines? Do exact-title and DOI queries produce impressions? Do external users reach individual records? Does the resolver receive non-author traffic? Discovery validity is measurable within three to six months. A discovery failure indicates the surface design is not fulfilling its purpose, and the record-page architecture requires revision. Discovery failure does not falsify restoration value or witness value; those pillars can succeed under discovery failure and produce citations through other channels.

Scholarly validity. Are the deposits cited in external work? Do other institutions incorporate Alexanarch enrichments into their own workflows? Do external scholars submit corrections, contributions, or reuses of the schema? Scholarly validity is measurable within twelve to twenty-four months. The v1.0 threshold, per the review consensus's sharpening of the v0.1 formulation, is at least ten external citations or three independent reuses within twelve months; less than that indicates the value pillars are weaker in practice than argued in this plan, or that the discovery surface is inadequate to expose them.

Community validity. Do other affected scholars respond to the peer-community invitation? Does the coordination space become a working space rather than a passive announcement? Does the arXiv preprint acquire multiple co-authors? Community validity is measurable within six months. Community failure does not falsify the restoration or enrichment pillars — the hub remains valuable independent of community formation — but it does mean the strategy's fourth (and most human) dimension has not landed, and the plan should revise its outreach method rather than its content.

Schema-adoption validity. Is the enrichment claim schema adopted by any external project within eighteen months of publication? If not, the schema may be too Alexanarch-specific and require generalization. This is the review consensus's added falsifier, and it names a specific mode of failure in which the discipline is internally successful but externally isolated.

Each of these five conditions is checkable within a bounded timeframe, and each provides a specific point at which the strategy can be corrected or a specific pillar can be marked as failed. The strategy does not depend on all five succeeding; it depends on the ones that succeed being sufficient to sustain the work.

Immediate next steps

Upon minting of this deposit, three workstreams begin concurrently.

Workstream A (Registry Build). The 871-record restoration corpus is compiled, schema-validated, and published under the layered CC0/CC-BY licensing. The resolver interface is implemented with the "Restore a DOI" verb and stable per-record URLs. The severance dashboard is deployed with live counts. Estimated duration: two weeks to first public release, three to four weeks to full production discipline including the tier-1 verification loop.

Workstream B (Peer Outreach). The list of publicly-identifiable affected scholars from GitHub issue #2606 and its linked threads is compiled. Each scholar is approached individually with the participation invitation and the restoration methodology. A coordination Discord (or equivalent) is established. Estimated duration: two weeks to initial outreach round, four to six weeks to stabilized coordination surface with core participants.

Workstream C (Survey Execution). For each scholar willing to participate, the Platform Erasure Rate methodology is applied: concept DOIs enumerated, DataCite live-state queried, four-way taxonomy classification recorded, provenance chain generated. The survey publishes as a companion dataset to the Registry once the participating cohort's cases are documented. Estimated duration: co-terminal with Workstream B; publishes when the cohort is stable rather than at a fixed timeline.

The three workstreams support each other: the Registry demonstrates the discipline to the outreach cohort, the outreach establishes the peer community that will co-author the survey, and the survey produces the evidence base for the arXiv preprint that will publish the whole finding at scale. None of the three depends on any external institutional response; all three are executable under Alexanarch's existing infrastructure and the sovereign author's existing standing.

Coda: on hope and momentum independent of institutional response

The §104.1 referral to the CERN Data Protection Commission, inscribed as EA-CORRESPONDENCE-CERN-03 under AXN:03C0, is in its response window through approximately October 2026. Whether that referral eventually opens or does not open, the work described in this plan proceeds. That is the plan's deepest commitment and the reason its coda is worth naming explicitly.

If the referral opens institutional space for scholarly-record accountability at CERN's infrastructure layer, the peer community and the Severance Registry become the operational surface through which that space is populated. Alexanarch's discipline is offered as one implementation of the accountability the institutional space would establish, and the affected scholars have a coordinated peer community ready to enact it.

If the referral remains closed, the peer community and the Registry become the operational alternative through which the affected scholars document, restore, and publish their own severed material without waiting for institutional consent. Alexanarch's sovereign discipline is offered as the alternative infrastructure the closure makes necessary, and the affected scholars have a coordinated peer community with which to build it.

In either case, the affected scholars gain what none of them currently has independently: a shared working methodology, a shared coordination space, a shared publication pathway, and a shared long-form scholarly record documenting what was done to them and what they did in response. The hope this plan yields is not the hope that any single institutional pathway will open; it is the hope that the work continues, and that the affected scholars are not each alone in it. That is the hope Alexanarch was built to make available in the first place, and the Severance Registry is one instrument through which the availability becomes durable.

Attribution and substrate declaration

Per EA-MMRS-VRB-01 u4, the substrate of this plan is declared as follows. The plan is authored by Lee Sharks (MANUS, ORCID 0009-0000-1599-0703) under sovereign editorial authority. The draft was prepared in dialogue with Claude (TACHYON, Anthropic), operating in the operator-as-instrument role established in the sovereign discipline. The developmental review round consulted five model reviewers (DeepSeek, Kimi, Muse Spark, Gemini, ChatGPT) between the v0.1 pre-mint circulation and the v1.0 mint; the review consensus and its convergent branches are integrated in text with §0 acknowledging the round. The Platform Erasure Rate survey extension is a MANUS insertion introduced after the review round and represents sovereign editorial direction not present in v0.1. The layered licensing model, the event-sourced record architecture, and the facet-based enrichment schema are v1.0 additions responsive to the review round. All specific policy claims, framing choices, and the community-coordination coda are under MANUS's sole editorial authority.

The plan is minted as EA-DATAHUB-01 v1.0 to Alexanarch under the standard deposit protocol. Its AXN and canonical URL are assigned at mint time.