1.1 — What This Volume Does With a Miracle

Here is a scene you have probably heard. An army stands on the southern tip of India. Across the water is the island of Lanka. There are no boats. So the monkeys write the name of Rama on stones, and the stones float, and the army walks across.

Here is what the oldest surviving version of the Ramayana actually says. The army has an engineer with it, a man named Nala, son of the divine craftsman. He is given command. For five days, a workforce of thousands cuts trees, drags boulders, and carries them to the shore. The text names the daily progress in a unit of distance — fourteen, twenty, twenty-one, twenty-two, twenty-three — as a foreman would record it. Ropes and measuring lines are used to keep the causeway straight. The materials sink. The bridge is built on top of them.

The floating stones are not in Valmiki. They arrive more than a thousand years later, in devotional retellings. The original is a construction log.

This is the pattern the whole volume runs on, so it is worth setting out completely on the first page.

The four questions

Every time this book meets something impossible, it puts the story through the same four questions in the same order.

One: what does the oldest layer of the text actually say? Not the version your grandmother told you, not the television serial, not the temple pamphlet. The earliest recoverable text. This alone dissolves a surprising number of miracles, because most of them were added by later hands who found the plain version insufficiently glorious. The floating stones are the clearest case. So is Draupadi's endless sari, which we will get to in 3.9 — the oldest manuscripts describe something considerably more disturbing and less magical.

Two: what would an honest witness have reported, given the words available to them? A person in 900 BCE who saw an aircraft would not report an aircraft. They would report a chariot that flies. A person who saw a chemical weapon would report a weapon that burned without fire and left the land barren for a generation, which is roughly what the Mahabharata does report. This question is not a licence to invent technology. It is a discipline: before deciding a report is fantasy, ask what a truthful person lacking your vocabulary would have said about the real thing.

Three: what physical event actually fits? This is where the volume does its work. There is a real chain of shoals between India and Sri Lanka, visible from orbit, and 2.13 goes through what it is made of and what building on it would involve. There is a real hill called Govardhan in Braj, and 4.4 goes through what happens when a herding community shelters under an overhang during a week of monsoon rain, and why the story is really about a tax revolt. There are rivers that go bad and are cleaned, mountains that were climbed, eclipses that arrived at useful moments.

Four — and this is the one that matters most: what does the story teach, whichever of the first three answers is right? Because the teaching does not depend on the mechanism. If the bridge was engineered, the lesson is that a huge coordinated effort by ordinary people beat an obstacle everyone called impossible. If the stones floated, the lesson is exactly the same. The moral payload of these stories is almost never carried by the miracle. It is carried by what somebody chose.

Why grounding is the respectful reading, not the cynical one

There is a common assumption that treating a sacred story as a record of real events, scaled up, is a way of attacking it. The opposite is true, and it is worth understanding why.

A miracle explains nothing and teaches nothing. If Rama crossed to Lanka because gods suspended physics for him, then his crossing is not an achievement and you cannot learn anything from it, because you do not have that option. If he crossed because he built a causeway with an army that trusted him, then you have a story about leadership, engineering and persistence that applies to you on a Tuesday morning.

And the miraculous reading is a much newer reading than people think. The oldest layers of these texts are far more sober than the popular versions. The magic accumulated, and 1.4 shows the exact mechanics by which it accumulated. Going back to the older, plainer version is not modernising the text. It is restoring it.

What grounding is not

Three failures to avoid, because each of them is common and each produces nonsense.

It is not "ancient India had aeroplanes and nuclear weapons." This claim gets made loudly and it is not supported. A flying chariot in a poem is a flying chariot in a poem. There is no archaeological trace, no metallurgical trace, no engineering lineage, and no supporting text of the kind that real technology always leaves behind. When this book says the causeway was probably built, it is because the text describes a construction process in construction language. When a text describes a chariot flying because a sage willed it, this book says that is a literary device, and says so plainly.

It is not "so it was all made up." The other failure. Troy was considered a fable until a businessman dug it up. The city of Dwarka, which 4.8 covers, has real submerged structures off the Gujarat coast, and the shoreline there has genuinely moved. The Kuru kingdom is attested in Vedic texts as a real political entity. The default assumption of this volume is that behind a very old story sits something that happened, distorted by twenty-five centuries of retelling — not that behind it sits nothing.

And it is not deciding in advance what the answer will be. Some things in these epics have a clean physical explanation. Some have a clean literary explanation. Some have neither, and the honest sentence is "we do not know what happened here, and here are the three candidate readings." That sentence appears in this volume a number of times, and it is not a failure. Pretending to certainty is the failure.

Worked example: the horse sacrifice that started the Ramayana

Dasharatha, king of Kosala, is old and has no son. He performs a great ritual and afterwards his three queens conceive. The devotional version: a divine being emerges from the fire holding a bowl of celestial payasam, the queens drink it, and gods are born as their children.

Put it through the four questions.

Oldest layer: the Ramayana describes two rituals, and the second is a putrakameshti, a rite explicitly performed for the desire of a son. It is conducted by a named priest, Rishyashringa, brought in from another kingdom specifically for it. The text records the enormous cost, the assembly of kings, and the political weight of the occasion.

Honest witness: an ageing king with three wives and no heir performs a state ritual of colossal expense, importing a specialist. Within a year, three of the queens are pregnant.

Physical fit: an old king's fertility problem is not mysterious, and neither is what a court might quietly do about the succession of a kingdom. The text does not say and this book will not invent. What is certain is that the ritual was a public political act — the whole point of doing it in front of assembled kings is that everybody sees the succession being secured.

And the teaching, which is what the chapter is actually for: the entire tragedy of the Ramayana grows from Dasharatha's desperation for sons and his inability afterwards to say no to any of the people who gave them to him. The miracle is decoration. The character flaw is the plot. He cannot refuse Kaikeyi, and four lives are ruined. That is in 2.4, and it does not need a single supernatural event.

The one place this book will not go

There is a line worth stating now.

This volume does not tell you whether God exists, and it does not tell you that these figures were or were not divine. That is not evasion, it is scope. A book cannot honestly settle the question, and pretending to settle it in either direction would poison every page after it.

What it does instead is separate two things that usually come glued together. Whether Rama was an incarnation of Vishnu is a question of faith, and you may answer it however you answer it. Whether Rama's decision to accept exile rather than let his father break a promise was right is a question you and I can actually examine, with reasons, from either side. This book works on the second kind of question relentlessly, and leaves the first kind to you.

If you hold these figures as divine, nothing here should offend you — the teaching is untouched and often sharpened. If you hold them as legend, nothing here demands belief. Both readers get the same book.

What to carry from this page

When somebody tells you a story you cannot believe, ask what the oldest version said. More often than you would expect, the oldest version is reasonable and somebody improved it later. This is true of religious stories, family stories, company founding stories and national histories alike.

Separate the mechanism from the meaning. Most arguments about sacred texts are arguments about mechanism, and both sides usually agree about the meaning without noticing.

And be equally suspicious of the two easy positions — "it is all literally true" and "it is all nonsense" — because both of them let you stop thinking, which is the one thing this material does not permit.

Next: 1.2 sorts out four words that get used as if they mean the same thing — itihasa, purana, myth and history — because the Ramayana calls itself one of them, and it is not the one you would guess.