David Uncovers the Abyss Beneath the Temple Mount

It began, as so many catastrophes do, with someone being told not to touch something and touching it anyway.

David was preparing the foundations for the Temple, the great house of God that his son Solomon would one day complete. He had the vision, the will, the resources, and the workers. The site was chosen. The ground had been surveyed. And so they began to dig.

Fifteen hundred cubits down, which is an almost incomprehensible depth, something unusual turned up. A shard. A fragment. An object that did not belong where it was found, or perhaps that belonged there more completely than anything else in the world.

David reached down to pick it up, because of course he did. And the shard spoke.

The Shard That Had Been There Since Sinai

Do not touch me, the shard said. Or rather, in the language preserved in Ginzberg's Legends of the Jews, compiled between 1909 and 1938 from the full breadth of rabbinic tradition: Thou canst not do it.

David, understandably, wanted an explanation. The shard provided one. It had been placed at that precise location to cover the tehom, the primordial deep, the chaotic waters that existed before creation, that God had held in check since the first day of the world's making. It had been there, the shard explained, since the moment at Sinai when God spoke the first words of the Ten Commandments, Anochi Adonai Elohecha, I am the Lord your God. The earth had trembled at those words and sunk, and the shard had been set in place to hold the boundary between the world and what lay beneath it.

The Zohar, composed in Castile around 1280 CE, returns often to this image of the deep, the formless dark beneath the ordered world that God subdued but never destroyed at creation. The waters of the tehom are not evil, exactly. They are prior to good and evil, prior to order and law. They are what the world rests on, and they require the world to rest on them in return. The shard was the seal on that agreement.

David listened to all of this and then lifted the shard anyway.

What Surged Upward When the Seal Was Broken

The waters of the tehom surged. The abyss opened. The ground that the workers stood on trembled as something enormous began to press upward from below, as if the earth's foundations were trying to breathe. The construction site became a catastrophe.

In the background, watching all of this with undisguised calculation, stood Ahithophel. David's advisor, one of the most brilliant minds in the kingdom, and one of the most treacherous. According to Ginzberg's retelling, Ahithophel saw the rising waters and thought: now David will meet his death, and I shall be king. He said nothing. He waited.

David, reading the room with the precision of a man who has survived court politics for decades, issued a warning that was really a demand. Anyone who knows how to stop this catastrophe and stays silent, he said, will one day throttle himself. He meant it. The pressure in that moment, the water rising, the earth shaking, the entire project threatening to undo not just the Temple but the world itself, made the threat feel like a kindness. Do something. Or face what happens when nothing is done.

Midrash Rabbah, in its 5th-century homiletical form, discusses the concept of shared responsibility for catastrophes that could be prevented. The tradition is not gentle on those who watch disaster approach and calculate their advantage instead of acting. Ahithophel, faced with David's ultimatum, stepped forward.

The Name That Stopped the Flood

What Ahithophel knew, what made him the only person in that moment who could stop the rising waters, was the ineffable Name of God. The Shem Hameforash. He inscribed it on a piece of pottery and threw it into the abyss, and the waters recognized the Name and subsided. Not because Ahithophel was righteous, because he was not. Because the Name carried its own authority regardless of the hand that wrote it. The Talmud Bavli, compiled in Babylonia in the 6th century CE, records extensive discussions about the Name and what happens when it is deployed. The waters of creation respond to it the way they responded at the beginning, with obedience.

Crisis averted. Almost.

Because now the waters had gone too deep. The moisture that sustains the earth, that feeds the roots of trees and keeps the ground from cracking into dust, was receding along with the chaos. One disaster had been replaced by a slower, quieter one. The land would dry out. The crops would fail. The world would not drown but wither.

How Fifteen Songs Brought the Water Back

David did what David does when he encounters something too large for ordinary solutions. He sang. He recited the fifteen Songs of Ascents, Shir Hama'alot, Psalms 120 through 134, and as he sang each one, the water rose one level, until it reached the proper depth that sustains life without overwhelming it.

Midrash Rabbah notes that these fifteen psalms have always carried a particular resonance, a sense of movement between depths and heights, between descending and ascending, between the place beneath the world and the place above it. They were written, the tradition suggests, for exactly this kind of moment, when the boundary between order and chaos has been disturbed and must be restored through prayer. Not through force. Through song.

The Legends of the Jews does not explain why David lifted the shard after being told not to. Perhaps the text considers this self-evident. He was building God's house. He believed the urgency of the project made him the right person to make that call. He was almost right. Almost. And the gap between almost and actually, that gap turned out to be fifteen psalms wide and as deep as creation itself.

The Temple foundations were eventually completed. Solomon would build what David prepared. But somewhere beneath the Temple Mount, a shard still rests, or perhaps a Name, inscribed on pottery, holding back the deep that has been pressing upward since Sinai. And David's fifteen songs float above it all, keeping the balance.