Post 5: The Case for a Leaner Code

How information overload complicated halacha… and why sovereignty requires a reset

In this post I’ll discuss why halacha has gotten complicated, why this is particularly problematic now, and how the problem can be addressed.

Three structural shifts since the onset of the industrial revolution have each independently been sufficient to accelerate halacha’s complexity.

First, the rate of genuinely novel halachic questions has increased as a consequence of technological change. For most of halachic history, the physical world presented a stable set of materials and processes: fire was fire, textiles were textiles, food preparation used heat and pressure and fermentation. So, for example, the melachot prohibited on Shabbat mapped onto these with reasonable stability. Beginning in the 19th century, new technologies began unbundling properties that had always traveled together. Fire, for instance, had always meant heat, light, combustion, and fuel consumption simultaneously. Incandescent bulbs separated combustion from the package. Fluorescent bulbs removed heat. LEDs removed both heat and combustion. Radiant heaters delivered heat without light. Each unbundling creates a question about the boundaries of the existing categories: which properties of fire are essential to the prohibition and which are incidental? Multiply this across every domain — food science, medicine, communications, manufacturing — and the volume of questions entering the gray areas of halacha grows rapidly.

This technology-driven conceptual fragmentation is compounded by a second, equally disruptive shift: the total transformation of the information environment in which poskim operate. Consider a rov in a mid-sized community in Poland or Morocco in, say, 1820. He has access to Shas Bavli, Rambam, Tur and Shulchan Aruch with whatever nosei keilim were in the editions that were available at the time, a few volumes of teshuvot, some rishonim and acharonim on Shas, and an assortment of other books that came his way. Even if he has access to a serious library, he most certainly doesn’t have a searchable database. When a novel question arises, he rules on the basis of what he has and his own judgment. His psak governs his community and generally affects no one else. The barriers to dissemination are high: copying is manual, distribution is slow, and most rulings never travel beyond the community that generated them. Different communities develop different practices, and the low interaction between them is a feature, not a bug: it keeps the system self-regulating. In this older world, a ruling wasn’t just a data point in a searchable index; it was a psak by a rov who knew his community, its character and its minhagim.

Fast-forward to the present. For all intents and purposes, the entire halachic literature has become accessible and searchable. The cost of publishing a sefer has collapsed. And the result, visible on the shelves of any seforim store, is hundreds of compendia covering increasingly narrow topics at increasing levels of detail. (I recently encountered a 530-page volume on the halachot of opening packages on Shabbat.) The economics of this are straightforward: when the entire literature is available, there is strong pressure to compile rather than to analyze. Compilation is safer: it is easier to defend exhaustiveness than a sharper definition. Proposing a sharper definition is riskier: it invites challenge from anyone with access to the same database. The rational strategy, especially for authors who are neither major poskim nor in a position to take intellectual risks, is to assemble cases and default to stringency, since leniency invites more scrutiny than strictness. The predictable result is a literature that grows without acquiring structure.

Third, these two shifts interact. Each new technology generates questions. Each question generates rulings. Each ruling, once published, becomes part of the literature that subsequent authors must account for. And because the literature lacks organizing principles – as we saw in the previous chapter with molid, uvdin d’chol, and hachana – each new entry makes the whole less coherent rather than more. The system doesn’t self-correct. It compounds.

***

The over-complication of halacha is particularly harmful now that Israel has become the center of Jewish life. This is not just a demographic fact: it transforms what halacha needs to be.

In the diaspora, the patchwork of Sephardi, Litvish, Chassidish, and Yemenite customs, each shaped by local conditions, was tolerable because these communities rarely needed to share a framework.

In Israel, none of this holds. Jews from every tradition live side by side and marry each other. Moreover, some form of Jewish tradition is gradually taking hold as a majority culture, something that couldn’t happen in the diaspora. A majority culture won’t function for long on a patchwork of diaspora customs developed under conditions that no longer exist. Different traditions are fine and should be respected and preserved, but a shared halachic foundation, a common core, is becoming a practical necessity. The ingathering of Jews from around the world is making such a common core both necessary and, for the first time since the dispersion, possible. Eden, the character from Part 1, was right about this much (though not about everything).

There is a subtler point. In the diaspora, complexity and stringency served a social function: they marked the boundary between inside and outside, signaling commitment and distinguishing the observant community from its surroundings. When Judaism is a majority culture, that signaling function is not merely unnecessary, but counterproductive. When stringency functions as identity marking rather than halachic substance, it actively repels people who want to do the right thing but are understandably not interested in navigating that maze.

There is another practical consequence. In a sovereign Jewish state, a significant part of the population will practice halacha not as a specialist discipline but as a cultural default, the way most Israelis already relate to Pesach, Yom Kippur, and Shabbat candles. For halacha to function as a default culture rather than a specialist pursuit, it needs to be performable with less conscious effort, internalized like a native language, not consulted like an acquired one.

In short, we have two problems that need to be solved. The foundation – the core of halacha that every Jew should be able to internalize – has become buried under layers of specialist literature until the two are indistinguishable. And the specialist literature itself, valuable as it is, has become unnavigable without years of training. The first problem calls for a leaner code: a reset of the foundation, thin enough to absorb, clear enough to build intuition. I’ll sketch the principles of such a code in the rest of this post and present a working prototype in the next. But the foundation alone isn’t enough. The entire literature must remain in play, because organic halachic development – the internalization phase – needs material to work with. The neglect of this process is what Eden got wrong. The second problem, then, is how to make the vast literature above the foundation accessible without letting it overwhelm the foundation. This calls for different kinds of tools that will be the subject of Axis 2.

***

Here are some principles for one possible simplified halachic code that every interested Jew could study, internalize and apply. Think of the goal as a distillation of each area of halacha that, if mastered, would make any halachic discussion in that area intelligible.

• The code aims to cover the complete foundations of a topic. Space is determined by what the issue requires for a clear statement of the principle, not by how commonly the issue arises in daily life. So, for example, the architectural methods that render an alleyway a permitted area for carrying objects on Shabbat (היתר מבוי), a topic only experts will ever need to consider, should get no less space than the melacha of makeh be-patish, which is the basis for many common Shabbat prohibitions.

• Where many cases or rules can be reduced to a single principle, only the principle need be cited. Examples should be mentioned only if they are needed to clarify the principle.

• The Rambam determines the baseline scope. Specifically, any case or rule that he omits can be omitted as inessential (with occasional exceptions).

• No disputes. Where there are disputes among the major poskim, resolve using a hierarchy of methods in the following order:

  • if the Rambam, Shulchan Aruch and Rema agree, ignore all other authorities;

  • if they disagree, but a clear consensus developed among later authorities, cite the consensus;

  • if there is no consensus and omitting the case is functionally equivalent to one of the opinions, omit the case;

  • more broadly, if one of the major opinions allows a simpler formulation, follow the simpler formulation;

  • if the above don’t hold and there is a formulation that is ambiguous on precisely the point of dispute, use that formulation (for example, a reshut harabim is rendered a permissible area for carrying if at its ends there are דלתות ננעלות, which means either doors that are closed or doors that can be closed, precisely the disputed point).

• Define concepts in a precise way that preempts contradictions within the code.

• Order the topics in a way that connects related topics, both to minimize repetition of principles and to maximize intuitiveness (for example, putting the rules regarding lighting of Shabbat candles with the mitzvah of honoring Shabbat of which candle-lighting is one instantiation, while putting restrictions regarding the use of the candles with the rabbinic extensions of the melacha of extinguishing fire).

• Every rule is attributed to the first of the major codifiers who cited it. In particular, if a later authority (usually, the Gra or Chazon Ish) proposed a novel formulation that subsumes multiple previously-cited rules in an elegant way, cite the simpler formulation with attribution to the authority who proposed it.

I acknowledge that other principles might be used towards the same end and that these principles leave lots of room for subjective choices in the implementation (and that I’m being a bit casual about entrenched differences between Sefardic and Ashkenazi rulings). Indulge me.

It’s also crucial to bear in mind that all the above is intended as the floor, not the ceiling. The code is the foundation. Above it lies the full specialist literature – the arguments, edge cases, minority opinions – which remains valuable and accessible, but is clearly marked as a different thing.

In the next post, I’ll deliver on my promise and present a working distillation of Hilchot Shabbat following the above principles. How to tame the specialist literature above the foundation is the subject of Axis 2, coming soon.