4.5 — Kaliya, Putana, and the Coded Stories

The childhood contains a long sequence of creatures sent to kill him. Most retellings run through them as a list of monsters. Read properly, they are three different kinds of story mixed together, and separating them is the point of this chapter.

Kaliya

A stretch of the Yamuna near Vrindavan has become poisonous. The water is black, the fish are dead, birds that fly over it fall, and cattle that drink from it die. The community has abandoned that part of the river entirely.

A serpent called Kaliya lives in the pool with his family. Krishna goes in, is nearly drowned, and finally dances on the serpent's hoods until it submits. He does not kill it. He sends it away — to the sea, in most versions — with its family, on the condition that it does not return.

The water clears.

The reading

Something was poisoning a stretch of river and it was identified and removed.

The candidates are ordinary. Effluent from a settlement or a workshop upstream — Mathura was a trading and manufacturing city, and dyeing, tanning and metalworking all produce exactly the kind of water the text describes. A natural source — decomposing matter in a stagnant backwater, an algal bloom, or a mineral seep. Or a genuine population of venomous snakes in a pool that people had stopped going near, which the local memory then merged with the poisoning.

Whatever the specific cause, the shape of the story is clean: a resource everybody had written off as permanently lost was investigated by one person who went in when everybody said not to, and the cause was removed rather than fought.

Why the ending matters

He does not kill Kaliya. This is the detail that makes the story worth keeping.

Kaliya explains himself. He came to that pool because he was being hunted elsewhere and had nowhere else to go. He is not malicious; he is displaced, and his presence is poisoning a river because that is what he is, not because of anything he intends.

And Krishna's solution is relocation, not destruction. The problem was that the serpent was in the wrong place. Moved, it is not a problem.

The general form, and it is genuinely useful: a great many things that are causing harm are not malicious, they are misplaced. The person destroying a team is often competent and in the wrong role. The habit wrecking your week is frequently a good habit at the wrong hour. The default response is to attack. The better first question is whether the thing is in the wrong place.

And this is one of the few stories in either epic where the correct response to an enemy is to relocate them rather than kill them. After Part 3, that is worth noticing.

Putana

She comes to Gokul disguised as a nurse, with poison on her breast, sent by Kamsa to kill the infant. The child feeds and kills her.

This is not a symbolic story and it does not need decoding. It is an assassination attempt on a hidden infant by an agent of a king who is killing children, and it failed. Poison was the standard method, and a wet nurse was the standard access.

What the tradition does with it afterwards is the interesting part. Krishna, having killed her, is said to have granted her the status of a mother — because whatever her intent, she gave him her breast. She receives funeral rites and, in the devotional reading, liberation.

That is a strange and rather beautiful piece of moral reasoning, and it is worth stating plainly: the tradition holds that an act of intimacy, performed with murderous intent, still counted for something. Not that her intent was excused. That the act itself was not nothing.

Where this lands in ordinary life: people do things for you for bad reasons — self-interest, guilt, obligation, calculation. The help was still help. You are entitled to be clear-eyed about the motive and you are not obliged to pretend the benefit did not occur. Holding both is more honest than either the naive version or the cynical one.

The animal killers

Bakasura as a crane. Aghasura as a great serpent whose open mouth the boys walk into thinking it is a cave. Trinavarta as a whirlwind that lifts the child away. Dhenukasura as a wild donkey in a fruit grove. Keshi as a horse.

These are the least individually meaningful stories and the most useful in aggregate, and the honest reading is:

A tyrant spent a decade trying to kill a child hidden in a herding village. Some attempts were assassins, some were animals in a landscape where children die of animals, and some were probably invented later to fill out a pattern that had already been established.

What is real is the pattern: a village hid a boy for years under a standing death sentence and kept him alive.

And that is a story about a community, not about a hero. Nanda, Yashoda, the cowherds, the women — every one of them was risking a king's retaliation to protect somebody else's child. The stories are told as the boy defeating monsters. The thing that actually happened is a village that did not give him up.

How to read a coded story: the four questions

Since this Part is full of them, here is the method, stated once.

Is anything at stake in the mechanism? In Kaliya, the poisoning is the story and the serpent is the vocabulary. In Putana, the poisoning is literal. Ask whether changing the mechanism changes the teaching. If not, the mechanism is decoration.

What was the physical situation? A poisoned river. A hidden child. A week of rain. Nearly every one of these stories has a completely ordinary situation underneath, and the ordinary situation is usually harder and more admirable than the miraculous version.

What does the ending choose? This is the most productive question. Kaliya is relocated rather than killed. Putana is honoured rather than left. Govardhan is a shelter rather than a battle. The endings are where the tradition's values are, and they are consistent.

And what is being left out of the popular telling? In every case here: the other people. The village that hid him. The community that sheltered under the ridge. The cowherds holding up their staffs. The retellings collapse a collective act into an individual one, which is the single most common distortion in the whole of hero literature.

Balarama

One figure who deserves rescuing from the margins.

Balarama is Krishna's elder brother, present in almost every story, and consistently written as the ordinary one — strong, direct, fond of drink, quick-tempered, and not subtle.

And he is the one who refuses to take part in the Mahabharata war (3.11). He taught both Bhima and Duryodhana the mace. He would not choose between his students, so he left on pilgrimage and came back when it was over. Then he was the only person on the field who publicly denounced the foul blow to Duryodhana's thigh (3.16).

The unsubtle brother is the only major figure in either epic whose hands are entirely clean, and he achieved that by declining to participate and saying so out loud.

The epic neither praises nor condemns him, and this book will say what it thinks: his position is defensible, it is not admirable, and it is not nothing. He kept his integrity by removing himself, which is a real option that real people take. It costs you the ability to affect the outcome, and it buys you the ability to say what you think about it afterwards, and whether that trade is worth making depends entirely on how much you could have affected the outcome.

What to carry from this page

Ask whether the harmful thing is malicious or misplaced. It changes the whole response, and the second is more common than the first.

Help given for a bad reason was still help. You may hold both facts.

Look for the collective act underneath the individual story. It is nearly always there, and finding it usually tells you more than the hero does.

And notice Balarama. In every conflict there is someone who will not take a side, and the interesting question is not whether that is cowardice — it is whether they say why, out loud, and whether they are willing to criticise the winners afterwards.

Next: 4.6 — Radha, the gopis, and the misconception about Krishna that will not die, answered directly.