Why the calendar remembers what the debates keep trying to forget. There are moments when the calendar tells the truth before the commentators do.
Tevet is one of those moments.
It is not merely “winter fasting.” It is a liturgical memory of siege, fracture, and darkness—a season where the covenant story feels thin in the hands, and where the community is forced to ask what it usually tries to avoid: Who guarded the oracle when the light was shortening? Who carried continuity when rival stories were forming, when power was re-narrating memory, and when the holy language itself—names, titles, roles—was becoming contested territory?
If you want to understand why “Notzrim” became such a volatile word, you don’t begin with modern polemics. You begin with the way the fast cycle holds a wound.
⸻
1) The fast cycle holds a wound before it gives an explanation (Tier 1)
The Tenth of Tevet (Asarah b’Tevet) is clear: it commemorates the beginning of Nebuchadnezzar’s siege of Jerusalem—the hinge that foreshadows destruction and exile.¹
But the Ninth of Tevet is different. It appears in the halakhic record as a fast day, yet the earliest layers preserve the reason as unknown—so unknown that later halakhic tradition can still state that “something happened” but does not give a definitive account of what.²
That matters. It means the calendar is doing something deeper than providing a history lesson. It is pinning a trauma to a date even as the community loses agreement on how to narrate it.
And here is the key move: when a day is kept as a fast while its “cause” becomes cloudy, later communities will do what communities always do—they will try to name the wound.
⸻
⸻
2) A Jerusalem “Simon” with real historical weight (Tier 1)
Before we chase later identifications, we need an anchor. Eusebius—drawing on earlier sources (notably Hegesippus)—reports that Symeon (Simeon), son of Clopas, who succeeded James in Jerusalem leadership, suffered martyrdom in a persecution under Trajan.³
Eusebius’ Chronicon tradition dates the martyrdom to the ninth or tenth year of Trajan, often correlated to AD 106/107.⁴
This is where the Jerusalem succession line stops being a romantic idea and becomes a historical claim with real footing: James → Simeon/Clopas belongs to the earliest strata of the movement’s memory, and it has its own integrity apart from later Roman monopolies.
You can speak of “Simeon” and “martyrdom” without having to collapse him into later Petrine framing—and without having to swallow every later legend that accretes around the name.
And that is exactly why the “Simon problem” becomes so important.
⸻
3) When memory tries to “name” the Ninth of Tevet (Tier 2)
Once the Ninth of Tevet is preserved as a fast day whose reason is unclear, the downstream tradition naturally begins to “fill in the blank.”
One common later explanation connects the Ninth of Tevet with the death of Ezra (and sometimes Nehemiah).⁵
But there is also another, more provocative downstream strand: a tradition that ties the Ninth of Tevet to a “Shimon” figure identified as Shimon Kefa / Shimon Hakalphus, sometimes explicitly connected to the “origin of Christianity,” and sometimes accompanied by the claim that the day’s reason was kept quiet to avoid retaliation under Christian rule.⁶
I am not presenting this as Tier-1 history. I’m presenting it as Tier-2 memory-work.
And it is exactly what you would expect if:
• Jewish communities were living downstream from a Christianized empire,
• the Notzrim question had become politically dangerous,
• and names and roles had become shorthand for boundary crises.
In other words: these traditions may not tell you “what happened on 9 Tevet” in a modern historiographical sense. But they absolutely tell you what later Jewish communities believed was at stake when they tried to explain the day.
And what is at stake is always the same: custodianship.
⸻
4) Tevet is a season of boundary-marking for a reason (Tier 1)
Tevet is not only about Jerusalem being sieged. It is also about the darkness of the world’s calendar and the contest over worship.
Avodah Zarah 8a tells a famous story: Adam sees the days shortening, fears the world is collapsing into darkness, and he fasts—then after the solstice he sees the days begin to lengthen and recognizes the cycle. The passage correlates this with pagan festivals: Saturnalia before the solstice and Kalenda after.⁷
That text gives you a Tier-1 footing for something bigger than date-keeping: Tevet is a season where Israel remembers the contest over time, worship, and covenant allegiance.
And that is precisely the kind of season in which the Notzri question becomes explosive. Because the Notzri question is not merely “Christology.” It is also:
• public identity,
• communal boundaries,
• liturgical exclusion,
• and who gets to claim continuity with Zion.
⸻
• public identity,
• communal boundaries,
• liturgical exclusion,
• and who gets to claim continuity with Zion.
⸻
5) The “Petter Chamor” lens as covenant grammar (Tier 3, grounded by Tier 1)
Here is where I state my framework plainly.
Modern readers treat “Peter” like a modern legal name. But in the first century, names function in layered ways: nicknames, titles, role-designations, polemical labels, and community memory all bleed together.
My claim is methodological: if you treat “Peter/Kephas” like a modern legal marker, you can end up “proving” whatever later tradition you already prefer.
That is why I use a covenantal grammar—what I call the Petter Chamor lens (firstborn redemption logic; Exodus 13:13)—not as “rabbinic doctrine,” but as a way of explaining why a “Peter” figure so easily becomes a symbol of boundary crossing, mediation, and redemption.
And once you grasp that, you can see why later memory-streams might try to attach “Shimon Kefa / Hakalphus” to a cryptic fast day: a contested role-name becomes a ritualized way of narrating the split—especially under conditions where speaking plainly could be dangerous.
This is not an argument for simplistic identification. It is an argument for disentangling names from roles and roles from later monopolies.
⸻
6) What can responsibly be claimed about “Rabbi St. Simeon Clopas” (Tier discipline)
This is where we refuse the shortcuts.
Tier 1: what is solid
• Asarah b’Tevet is the siege fast.¹
• Ninth of Tevet is preserved as a fast day whose reason is “unknown” in the early record.²
• Avodah Zarah 8a frames solstice time as a contest of worship and calendar culture.⁷
• Eusebius preserves Simeon son of Clopas as a Jerusalem leader and martyr under Trajan, with a Chronicon dating to Trajan’s ninth/tenth year.³⁴
Tier 2: what is later memory-work (and why it matters)
• Later streams attempt to name the Ninth of Tevet (Ezra, etc.).⁵
• Some later streams tie 9 Tevet to a “Shimon Kefa / Hakalphus” tradition and explain secrecy as prudence under Christian rule.⁶
• Later streams attempt to name the Ninth of Tevet (Ezra, etc.).⁵
• Some later streams tie 9 Tevet to a “Shimon Kefa / Hakalphus” tradition and explain secrecy as prudence under Christian rule.⁶
Tier 3: what is my reconstruction / Messianic Noahide framing
Here is where I use honorific language (“Rabbi,” “saint”) and interpretive claims (Notzri retrieval, oracle keeper continuity, role-name analysis, Petter Chamor typology). This is not mainstream Jewish canonization, and it is not presented as baseline Eusebian history. It is an interpretive project grounded in Tier-1 and Tier-2 materials.
That discipline does not weaken the argument—it strengthens it. It tells the reader: I know what I’m doing with sources. I’m not confusing my theology with my chronology.
⸻
7) Why this matters for Notzri “purity” and covenant guardianship (the landing)
This is not calendar trivia.
The word Notzrim became a flashpoint because it touched custodianship:
• Who guards the covenant story?
• Who guards the oracle?
• Who holds continuity with Zion when the world re-narrates everything?
The Tevet cycle stages that drama:
• Siege and exile (10 Tevet)
• A cryptic “loss” (9 Tevet) preserved as a fast even when the reason becomes unclear
• A solstice contest over worship and assimilation (Avodah Zarah 8a)
• A cryptic “loss” (9 Tevet) preserved as a fast even when the reason becomes unclear
• A solstice contest over worship and assimilation (Avodah Zarah 8a)
And then the Jerusalem line confronts us with an uncomfortable truth: the earliest movement was not “Christianity” as later empire defined it. It was a contested, Jerusalem-centered witness carried by real people with real succession lines—James, Simeon/Clopas—and later history fought over how to name them, where to place them, and what to do with the Notzri word itself.
So Tevet becomes a school for Messianic Noahides: a season for sobriety, humility, and refusal of conflation. A season to honor the Jerusalem line without weaponizing it. A season to remember that the “watchers of the covenant” are not those who win the propaganda war, but those who keep faith when the days are short—until God lengthens them again.
⸻
⸻
Endnotes
1. Ohr Somayach, Insights into Halacha: “The Many Facets of Asarah B’Teves.”
1. Ohr Somayach, Insights into Halacha: “The Many Facets of Asarah B’Teves.”
2. Shulchan Aruch O.C. 580: the Ninth of Tevet is recorded as a fast day, with the specific “trouble” described as unknown; see discussion summarized in “The 9th of Teves: A Fast Day?”
3. Eusebius, Ecclesiastical History 3.32 (Symeon son of Clopas martyrdom under Trajan).
4. Loeb Classical Library note: Chronicon dating of Symeon’s martyrdom in Trajan’s ninth or tenth year (AD 106/107).
5. Later explanatory streams connecting 9 Tevet to Ezra (and sometimes Nehemiah).
6. Later tradition associating 9 Tevet with “Shimon Kipa/Shimon Kefa,” and explaining secrecy as prudence under Christian rule.
7. Avodah Zarah 8a on Adam, solstice, Saturnalia and Kalenda.
