Watch this volume try to fix something and you will notice it never actually does.
A curse cannot be withdrawn. An estrangement cannot be healed. A body cannot be put back. And in every case the resolution is the same move, which is not a repair at all:
the damage is converted into a permanent institution and scheduled.
Chandra is cursed with consumption and Śiva cannot lift it. So:
"O Chandra! During one fortnight, every day, you will decline by one digit. In another fortnight, you will constantly increase by one digit."1
That is the lunar cycle. The moon's phases, in this text, are an unhealed curse running on a timetable.
Once you have seen it there you see it everywhere, and it runs in four different output formats.
A calendar. Kārttikeya walks out on his parents permanently, so the estrangement becomes a visiting rota — "On the day of amavasya, Shambhu himself goes there. On the day of purnima, Parvati certainly goes there" — plus a public slot in Kārtika.2 Chandra's consumption becomes the lunar fortnight.1 Gaṅgā, saturated with the sins she has absorbed from bathers, contracts an annual cleaning visit: "on that day, every year, Ganga goes there to cleanse the sins she has accepted from men."3 And Volume 1's Padmā, unable to withdraw her curse on dharma, converts it into a four-yuga schedule with a reset.
A shrine. Gajāsura, impaled, asks for his own hide to be worn and his body becomes Kṛttivāseśvara.4 The ball Pārvatī kills two demons with becomes Kaṇḍukeśvara.5 Śukra, swallowed and expelled through Śiva's penis, gets Śukreśa.6 The pond where a murdered boy's dismembered body was thrown becomes Śivālaya, and the murder produces Ghuṣmeśa.7 Agni's twelve-month austerity ladder produces Agnīśvara.8
A prohibition. Tulasī grows on Vrindā's pyre and "with the exception of Ganesha, it pleases everyone."9 Conch shells are made from Śaṅkhacūḍa's bones and "with the exception of Shankara, water from a conch shell is pleasant to everyone."10 Two standing exclusions in living practice, both derived from the volume's two impersonation-rapes.
A name. And here the plan this build was working from needs correcting.
The Phase 1 record states that "nearly every name-origin in the volume is derived from an injury, a death, a mutilation or a crime", on the strength of nine sampled etiologies of which nine were injury-derived.
Nine out of nine is not evidence, because the nine were selected for being injury-derived. That is sampling on the outcome, and it can only ever return the answer it started with.
Swept properly — the whole body, for the naming constructions the text actually uses (will be known as, came to be known as, famous under the name) — the picture is different.11
The sweep returns 32 naming instances across 26 chapters. Of those, injury-, death-, mutilation- or crime-derived: Jalandhara (throttled Brahmā until he wept), Kīrtimukha (ate his own body), varvarī (condemned out of Lakṣmī's jealousy), the śālagrāma (Viṣṇu cursed to stone and bored by worms), Śukra and Śukreśa, Kṛttivāseśvara, Kaṇḍukeśvara, Ketu (Rāhu's severed head), Jīva (for saving Indra from execution), Ghuṣmeśa and Śivālaya. That is roughly eleven of twenty-six.
Against them, plainly non-injury names: Kālabhairava, derived from a quality — "Since you blazed like Kala, you are yourself Kalaraja… Since you terrify Kala, you will be Kalabhairava." Kālāgni, the same. Avimukta, from the kṣetra's unknowability. Gaṅgādvāra, Tryambaka, Rāmeśvara, from events rather than harms. And the whole Vyāsa-lineage roll at ch 233–234 — Suhotra, Kaṅka, Gautama — which are charter names with no story attached at all.
So the corrected claim is narrower and it is still worth having:
Within narrative name-origins — where a being or a shrine is named for something that happened — injury-derivation dominates. Across all naming in the volume it does not, because the volume also names by quality, by place, and by lineage catalogue, and those are the majority.
[n≥3 PATTERN] for the narrative subset. Not a claim about name-origins generally, and the earlier version should not be cited forward.
Chandra's case repays isolating, because it is the only one where the schedule is a thing everybody can see.
The setup is unremarkable by this volume's standards: Dakṣa curses him with consumption, and Brahmā first recites Chandra's prior offences — the abduction of Tārā, the disputed foetus, the deva–daitya war it caused — as context for the sentence.1 The volume audits its defendants before sentencing, as it does with Andhaka and Satyaratha.
What is remarkable is the resolution. Śiva does not lift the curse. He does not overturn Dakṣa. He makes it periodic — decline for a fortnight, increase for a fortnight, forever.
Three things follow.
The curse remains in force permanently. Chandra is not cured; he is consumed on a fixed schedule and restored on a fixed schedule, and the consumption never stops happening.
The affliction becomes the timekeeper. Every ritual in this text that runs on tithi, on pakṣa, on amāvasyā or pūrṇimā — which is most of them, including Gaṇeśa's caturthī, Śivarātri, and the Kālabhairava vrata — is calibrated against a wound.
And nobody in the text remarks on it. The chapter is called the greatness of the Somanātha jyotirliṅga, and the lunar cycle arrives as a piece of shrine-etiology, not as cosmology.
That is the mechanism at its purest: an unhealable injury, converted into a permanent, publicly visible, universally used institution — and reclassified as a benefit in the process.
The move is not a failure of imagination, and reading it as one misses what it does.
What it buys is closure without resolution. A curse that cannot be withdrawn is a live problem forever; a curse on a schedule is a fixed feature. Nobody has to be forgiven, nobody has to admit anything, no principle has to be revised. The parties simply stop being in a dispute and start being in a calendar.
Kārttikeya's case shows this exactly. He is not reconciled with his parents — the estrangement is explicitly permanent, "he is there even now", and when they arrive he moves three yojanas further off. What the schedule produces is not a repaired family but a workable arrangement: alternate lunar halves, and a pilgrimage season built on top.
What it costs is that the injury becomes compulsory for everyone else. The ritual exclusions are the clearest instance. Two women were raped by a god in disguise; the resulting rule is that a Śaiva may not offer Śiva conch-water and a Gāṇapatya may not offer Gaṇeśa tulasī. Practitioners perform those exclusions daily, for reasons the practice does not carry — the liturgy transmits the injury forward as a rule while dropping the story that would explain it.
⚑ Which is the sharpest thing on this page. The institution outlives the memory of the damage. The person handling a conch, or watching for a new moon, or leaving tulasī off a Gaṇeśa altar, is enacting a settlement in a case they have never heard of. The damage is fully preserved, structurally, and fully invisible.
Something has happened that cannot be undone, and everybody has stopped talking about fixing it.
A falling-out that will not mend. A decision that cost somebody something permanent. A departure nobody is going to reverse.
Watch for what comes next, because it is nearly always the same and it is nearly always presented as a solution.
Somebody proposes a schedule. Alternate Christmases. A standing monthly call. An annual review of the thing that went wrong. A commemorative event.
That is the conversion, and here is the honest assessment of it, which is not the cynical one: it usually works, and it works precisely because it is not a repair. Kārttikeya's parents get to see their son. The arrangement is real. Nobody has to apologise, nobody has to concede, and the relationship continues in a reduced and durable form. For an injury that genuinely cannot be undone, a schedule is often the best available object.
So the question is not whether to do it. It is: say out loud what is being scheduled, once, before you schedule it.
Because the failure mode is the ritual exclusions. Two generations on, the arrangement is still running and nobody remembers what it settled. The family that alternates Christmases has a rule, an etiquette, and a set of feelings about it, and no one under thirty knows what happened. The rule is doing its work perfectly and transmitting an injury that nobody can name or examine.
One sentence prevents that, and it costs nothing: this is what we're doing instead of fixing X. Say it, write it down somewhere the next people will find it, and then keep the schedule.
And if you are on the receiving end of a new arrangement you did not ask for — the standing meeting, the annual gesture — the useful question is the same one in reverse: what is this instead of? There is always an answer, and being told it is the difference between a settlement and a rule you have merely inherited.
Two limits, stated so the finding is not stretched.
The volume does have a repair mechanism and uses it. Andhaka is impaled, revived, restored to health and made a gaṇapati. Bāṇa is mutilated and promoted. The Nṛsiṃha of ch 216 is cursed, swallowed, and rehabilitated at Badarī. These are not schedules; they are outcomes in which the damaged party is put back and the matter genuinely ends.
⚑ And the discriminating variable is visible: the repairs go to parties who repent while still alive and ask for a relation. The conversions go to injuries where nobody can repent — a curse pronounced by a third party, an estrangement caused by deception, a body already destroyed. The volume repairs relationships and schedules conditions.
And the conversion is not always to the victim's benefit. Chandra gets a permanent affliction rebranded as a cycle. Śukra gets a planet and a travel-taboo attached to his own glance. Gajāsura's corpse becomes a liṅga and a name for the god who killed him, at his own request. Whether these are compensations or trophies is not something the text separates, and this page does not either.
⚑ ENRICHED 2026-08-11 — and the pattern survives both limits, because Volume 3 reproduces it independently at roughly seventeen instances. Volume 3 was censused for name-etiologies without reference to this page's list. It returns roughly seventeen, of which fifteen derive from an injury, a killing, a crime or a catastrophe — an independent reproduction of the ratio this page established at nine of nine.V1
From a killing: Durgā (from the daitya Durgama) · Sarasvatī ("the destroyer of Shumbha asura… She is spoken of as Sarasvati") · Dhūmāvatī (from the smoke of the messenger she incinerated by huṃkāra) · Dhundhumāra (from the buried danava whose annual breathing shook the earth) · Vṛṣaghna · plus three promised future names — Nandajā, Bhrāmarī, Bhīmā Devī — all from killings not yet committed.
From catastrophe or injury: Śatākṣī (she wept for nine days and the innumerable eyes are the name) · Śākambharī ("When vegetables died in the world, you revived them from your own body") · Kālī and Kauśikī (from Gaurī's shed skin) · Gālava.
From a crime: Triśaṅku · Śaśāda.
From transformation under curse: Bahudā · Yamunā.
The only two exceptions in the entire volume are Guha (from a conversion) and Somanandi (from service).
⚑ Three of the seventeen arrive in one paragraph. Ch 363-6(51) has the devas name Devī three times in a single speech, each time from a disaster she has just ended.V1
And Volume 3 supplies two species this page's Volume 2 material does not have.
⭐ The name that displaces the real one. Pṛṣadhra kills a bull by accident — his guru finds explicitly that he "had committed the sin inadvertently and not voluntarily" and demotes him anyway — and endnote 1388 records what happens to the name: *"Vrishaghna — the one who killed a bull, so named because of what he did. His actual name was Prishadhra."* ⚑ The body then uses the crime-name throughout.V2 Every other instance in this page's catalogue adds a name. This one overwrites. [n=1 OBSERVED].
⭐ And the name conferred before the deed. Dhundhumāra is announced three times in advance — by the narrator, by the father handing over the commission ("there is no doubt that this son of mine will become Dhundhumara"), and by a voice from the firmament ("This prosperous prince will become Dhundumara now") — and only then does the killing happen.V3 ⚑ A prospective damage-name is a prophecy wearing an etiology's clothes, and the two are indistinguishable in the finished text. Also [n=1 OBSERVED].
⛔ What the enrichment does not do. It does not raise the ratio into a stronger register. Two volumes independently producing the same lopsided distribution is a genuine convergence, and [n≥3 PATTERN] is where it stays — the interesting thing is that neither volume ever remarks on it, and that the one instance which overwrites a name and the one which precedes the deed are the two that most resist the page's own account of what a conversion is for.
There is a detail running through the shrine strand that changes how the conversions read, and it is easy to miss because it is always in the victim's own mouth.
They request it.
Gajāsura, impaled on the trident, asks for two things: that Śiva wear his hide — "It is pleasant to the touch… Let it always be your ornament" — and that Śiva take his name, becoming Kṛttivāsa. Both are granted, and his body becomes the liṅga.4
Ghuṣmā, offered any boon after her son is restored, spends it on the shrine: "for the protection of the worlds, please remain established here, under my name." And Śiva agrees in the same terms — "I will remain here, under your name."7
Śukra, having been swallowed and expelled, is renamed for the manner of it by Śiva and accepts it, prostrating.6
Even Chandra's case has the form of a petition answered, not a sentence imposed: the gods intercede, and what Śiva produces is the periodicity.1
⚑ That matters for how the mechanism should be described. It is not straightforwardly extraction. The injured party is offered something, and what they ask for is the conversion of their own damage into a permanent public object — a name, a shrine, a place in the calendar.
Two readings are available and the volume supports both without choosing.
The generous one: this is what compensation looks like when nothing can be undone. Gajāsura cannot be unkilled, so the most that can be salvaged is that the killing produce something enduring with his name on it. Asking for the shrine is the rational move for someone with no other currency left.
The harder one: the request is itself produced by the situation. A man on a trident, praising the god who put him there, asking that his skin be worn — this is the same machine that has Tārakākṣa thanking Śiva while burning and Nṛsiṃha pre-authorising his own beating. The volume's victims reliably endorse their treatment, and endorsement is what converts an injury into an institution nobody has to answer for.
The page does not resolve that, because the text does not. What can be said flatly is that the conversion is almost never imposed on a silent party — it is transacted, in words, with the person the damage happened to, and their consent is on the page.
The strongest evidence is the calendar strand, because all four instances are explicit schedules with stated periodicities, and one of them is the lunar cycle.123 Nothing there requires interpretation.
Tension 1 — the etiology count was overstated in this build's own record, by sampling on the outcome.11 Corrected above; the narrower claim survives and the broader one does not.
Tension 2 — the exclusions transmit the injury and lose the story.910 The volume does not remark on this and shows no awareness that a rule can outlive its reason.
Tension 3 — conversion and repair coexist and the volume never contrasts them. Andhaka is genuinely restored; Chandra is genuinely not. Both are called favours.
Tension 4 — some conversions look like trophies. Śiva wears Gajāsura's hide and takes his epithet, at the victim's request, from a corpse on a trident. Compensation and appropriation are not distinguished.
Open question. Every conversion in the volume produces something a third party then uses — a date, a shrine, a rule. Is there a single case where the damage is converted into something only the injured party benefits from?
Against Kumāra, and the Son Who Left: the amāvasyā/pūrṇimā schedule is worked there as the end of a family story and here as an instance of a general method. Read together, the point is that the volume produced the same object for a broken family and for a cursed planet.
Against The Two Wives Who Were the Weak Point: the two ritual exclusions belong to that episode and are the strand's clearest case of an injury outliving its story. That page holds the crimes; this one holds what the liturgy did with them.
Against Worship Me First, or Nothing Counts: the same conversion in the ritual register. Every holder of ritual precedence was injured into it, and precedence is the compensation — an injury converted into a permanent lien rather than into a date or a shrine.
Against Andhaka, and the Clause He Wrote Himself: the counter-case, and it defines the boundary. Andhaka is genuinely repaired because he repents alive and asks for a relation. The conversions happen where that route is closed.
Against Padmā's Curse and the Four Yugas: the Volume 1 instance, and the one that establishes the move predates this volume. Its endnote marks the attribution as local to that passage, which is worth carrying — the mechanism recurs; a single doctrine of it does not.
Why Dehumanization Precedes Atrocity — that page's method is its transferable part: establishing that a sequence holds by finding cases where the ordering is visible and the concealment is absent.
The conversion mechanism invites the same treatment and yields a comparable result. Across four output formats — calendar, shrine, prohibition, name — the ordering is always injury first, institution second, explanation optional. And the volume, like the historical cases that page examines, is not hiding it: the etiology is usually stated in the same breath as the institution. Conch shells are from Śaṅkhacūḍa's bones; the rule about Śaṅkara follows in the next clause.
What the pairing produces is about what survives transmission. In the historical material the difficulty is that perpetrators destroy the record, so the ordering has to be reconstructed. Here the record is fully preserved and the ordering is still lost — not by suppression but by format. A rule travels; a story does not. A date travels; a grievance does not. The institution is exactly the part that propagates, and the injury it encodes is exactly the part that drops out, because practice transmits procedure and not provenance.
That suggests a different place to look in the historical cases. Alongside asking what was destroyed, ask what was institutionalised — because a settlement, a commemoration, an exclusion or a calendar may be carrying the ordering forward intact, in a form nobody reads as evidence because everybody experiences it as ordinary practice.
One handshake, not two. A second would restate the workflow's point about arrangements outliving their reasons, and the page already carries that argument in its own voice.
Sharpest implication. This corpus has no repair mechanism for anything a third party did. A curse cannot be lifted, an estrangement cannot be healed, a body cannot be restored — so the damage is converted into a permanent institution and put on a schedule, and then called a favour. The moon's phases are a curse of consumption running on a fortnightly cycle. A son's refusal to come home is a visiting rota that the pilgrimage year is built on. Two rapes are the reason a Śaiva does not offer conch-water and a Gāṇapatya does not offer tulasī. Every one of those is still in operation, and in every case the practice has outlived the story that produced it — which is the mechanism's real product. The injury is preserved perfectly, in a form nobody can read.
Generative questions.