This week, the new lunar month announced both Ramzan and the month of Adar, the twelfth month in the Jewish lunar year. Two calendars turning on the same moon. That is not coincidence. It is shared inheritance – a rhythm of sacred time that predates borders and outlives empires.

The ancient method of announcing a new moon required witnesses. Sacred time depended on human eyes.

In both traditions, the new month was never merely observed – it was declared. In the classical Jewish system, two witnesses who had seen the first sliver of the moon testified before a court, and the month was fixed by a legal utterance: mekudash, sanctified. The word is not poetic. It is juridical. It is the same language that consecrates a Jewish marriage.

Advertisement

In Islam, the month turns on ruʾyat al-hilāl, the sighting of the crescent, reported and confirmed through communal authority and then announced publicly. The moon is the same. The mechanism is the same. Sacred time becomes real because human beings look up, testify, and speak.

This essay begins with shared astronomy, but continues with shared gastronomy – with what happens in the ritual pot when sacred time approaches.

It is also about names that travelled with the Jewish community from Baghdad to Calcutta – from harisa to haleem, and from t’beet to hameem – and about a theory that may not yet be provable, but is too coherent to ignore.

Advertisement

A question demands an answer: why would a community that carried an established dish with an established name from the Middle East to India allow that name to shift? Why does t’beet become hameem? No one has offered a satisfying explanation. So I began to look for one.

A Sabbath dish

In Baghdad, the Sabbath dish had a name that belonged to the alleyways: t’beet. From the Arabic root meaning “to spend the night”, it described exactly what it did. The chicken was stuffed. The pot was sealed. It remained in the embers until Shabbat noon. The name referred to the action. It was local. Intimate.

In the Halachic language of Jewish law, this kind of pot belonged to a broader category: ḥamin – “the warm things”. Already in the Mishnah – the early rabbinic compilation of Jewish law – ḥamin appears as the legal designation for food prepared before Shabbat and left insulated to carry sacred time through the night.

Advertisement

The Sabbath stew prepared before sundown and left to cook overnight has many names. In Europe it is cholent; among Jews shaped by Iberian exile it is known as ḥamin. What you call it reveals where you come from.

Claudia Roden, in The Book of Jewish Food, places Baghdadi t’beet, ḥamin, and harisa – the wheat-and-meat porridge of Abbasid kitchens, not the Tunisian chili paste – within the same structural family. Ingredients vary. Textures vary. But the grammar is shared: grain, meat, low heat, sacred rhythm.

So we begin not with flavour, but with structure.

Advertisement

In medieval Baghdad, harisa – wheat and meat pounded into porridge – simmered for Ramzan iftar. Among Iraqi Jews, t’beet – rice and stuffed chicken – crossed the night for Shabbat lunch.

Harisa and t’beet shared lineage long before they shared geography.

The name harisa derives from the Arabic root meaning to pound or crush – the technique that defines the dish. In contrast, t’beet takes its name from spending the night, and ḥamin from warmth itself.

Each name encodes a different organising principle: harisa for what is done to it, t’beet for how long it rests, ḥamin for the heat it retains.

Advertisement

One was emulsified into paste. One was layered rice. Both were ritual foods governed by sacred time. Both trusted patience.

Arab trade and Jewish migration carried these foods across oceans to India.

When Baghdadi Jews arrived in Bombay, Calcutta, Rangoon, and Cochin in the eighteenth and nineteenth centuries, they entered a region already saturated with Arab culinary memory. On the Malabar Coast, Muslim Mappila communities prepared haris, wheat-and-meat stews tracing back to the same Abbasid grain tradition.

Advertisement

In Hyderabad, Arab settlers under the Nizams brought harees, which evolved into what became known as haleem – wheat, lentils, and meat pounded with spice into a dense, deeply seasoned paste.

The soundscape was already in place.

Harees. Haris. Haleem.

The question, then, is this:

Why, in India, did the Baghdadi name t’beet – still widely used elsewhere – shift only there? And why did it settle into hameem, not ḥamin – a form that sits audibly beside haleem – inside a community that already possessed a long-standing category for the Sabbath overnight pot?

Advertisement

Here the argument must be precise.

This is not an etymological claim.

It is an acoustic one.

The form “hameem”, as it stabilised in India, reflects pronunciation settling within a shared culinary environment – one shaped by Jewish households and Muslim cooks working in close proximity. It concerns sound adapting within a shared auditory space, not lexical borrowing.

Jewish families brought Sabbath traditions and t’beet with them. In colonial India, within a shared Islamicate culinary climate shaped by centuries of grain-and-night cooking, Jewish and Muslim ritual stews developed side by side.

Hyderabadi haleem: wheat and meat pounded into paste. Credit: Elli Benaiah

Food researcher Joel Haber has pointed to examples outside India – in Turkish Sephardi usage and in Italian Jewish usage – confirming that ḥamim is a long-standing Jewish category term. In those cases, the final “m” reflects the plural.

Advertisement

In India, however, hameem performed different work. The Jewish Sabbath pot entered a soundscape already occupied by haleem – the night-crossing grain stew of Ramzan. Two sacred pots. Two communities. One ritual technology of slow grain cooking tied to sacred time. Often, one cook.

The dishes remained distinct.

Indian Jewish hameem remained rice-based, layered, caramelised, producing hakaka at the bottom of the pot. It was not pounded wheat. It was not emulsified paste.

The structure stayed Halachic. The grain remained layered.

Advertisement

Only the name shifted.

Family memory clarifies how. Muslim cooks were often employed in Jewish homes because they were knowledgeable in matters of meat. A skilled cook, once found, moved from household to household by reputation. In these kitchens, technique was transmitted orally. Sacred time was prepared in a shared culinary language.

In Hyderabad and Malabar, harees and haleem crossed the night for iftar. In Calcutta and Cochin, hameem crossed the night for Shabbat lunch.

The technique differed. The grain differed. But the ritual grammar - low fire, patience, sacred time - was shared.

Advertisement

The convergence was acoustic, not culinary.

Within the port-city ear, hameem became locally legible – not borrowed, not assimilated, but resonant.

From Abbasid harisa to Iraqi t’beetbto Indian hameembalongside Malabar haris and Hyderabadi haleem – not one dish becoming another.

But names adjusting within a shared soundscape.

Two calendars.

One moon.

One night-crossing pot.

And in the Indian culinary melting pot – patient, sealed, faithful – no translation was needed.

Elli Benaiah writes on Jewish diaspora food history and is currently working on a book exploring Jewish culinary networks across South and Southeast Asia.

This article first appeared on Elli Benaiah’s blog, Beyond Bablylon: Jewish Food Stories from Southeast Asia.