<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN""http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Aspaqlaria</title>
</head>
<body>
<style type="text/css">
h1 a:hover {background-color:#888;color:#fff ! important;}
div#emailbody table#itemcontentlist tr td div ul {
list-style-type:square;
padding-left:1em;
}
div#emailbody table#itemcontentlist tr td div blockquote {
padding-left:6px;
border-left: 6px solid #dadada;
margin-left:1em;
}
div#emailbody table#itemcontentlist tr td div li {
margin-bottom:1em;
margin-left:1em;
}
table#itemcontentlist tr td a:link, table#itemcontentlist tr td a:visited, table#itemcontentlist tr td a:active {
color:#000099;
font-weight:bold;
text-decoration:none;
}
img {border:none;}
</style>
<div xmlns="http://www.w3.org/1999/xhtml" id="emailbody" style="margin:0 2em;font-family:Times New Roman, Times, serif;line-height:140%;font-size:12px;color:#000000;">
<table style="border:0;padding:0;margin:0;width:100%">
<tr>
<td width="99%" style="vertical-align:top">
<h1 style="margin:0;padding-bottom:6px;">
<a style="color:#888;font-size:22px;font-family:Trebuchet MS, Arial, sans-serif;font-weight:normal;text-decoration:none;" href="http://www.aishdas.org/asp" title="(http://www.aishdas.org/asp)">Aspaqlaria</a>
</h1>
</td><td width="1%"></td>
</tr>
</table>
<table id="itemcontentlist" style="clear:both;padding-top:.5em;border-top:1px solid #999;">
<tr>
<td style=" margin-bottom:0;line-height:1.4em;">
<p xmlns="" style="margin:1em 0 3px 0;line-height:115%;">
<a style="font-family:Trebuchet MS, Arial, sans-serif;font-size:18px;" href="http://feeds.feedburner.com/~r/Aspaqlaria/~3/189094938/halachic-process-part-i.shtml">Halachic Process, part I</a>
</p>
<p style="font-size:12px;color:#555;margin:9px 0 3px 0;font-family:Times New Roman, Times, serif;line-height:140%;font-size:12px;">
<span>Posted:</span> 22 Nov 2007 07:57 PM CST</p>
<div style="margin:0;font-family:Times New Roman, Times, serif;line-height:140%;font-size:12px;color:#000000;"><p>“<em>Eilu va’eilu divrei E-lokim Chaim, vehalakhah keBeis Hillel</em> — These and those are the words of the ‘Living’ G-d, but the <em>halakhah</em> is like Beis Hillel.” The voice rung out from heaven that even though the law is ruled according to Beis Hillel, Beis Shammai’s position is also the word of G-d. There is some variation in <em>halakhah</em> between people — and yet both are right. We can’t expect every halachic decisor to take the same data and reach the same conclusion, even if no one errs. In the past, we compared different models for explaining how multiple correct answers could coexist. Here that would keep the conversation too broad. I will instead just explore the problem from the Maharal’s perspective.</p>
<p>The Maharal’s position is that “<em>divrei E-lokim Chaim</em> — the word of the ‘Living’ G-d” is simply too rich and too complex to exist in this world. Therefore they are mapped to oversimplified models, related to Hashem’s words the way a shadow is a flattened representation of the original. And thus, different people looking at the problem from different directions will get different shadows — even though they are all accurate representations of the same thing.</p>
<p>To finish out the metaphor: The angle at which we look at <em>Devar Hashem</em> is our “<em>derekh</em>“, our path in how we . This <em>derekh</em>, just like the lamp, is determined by two things: <em>mei’ayin basa, ule’an ata holeikh</em> — from where do you come, and to where are you going? Where the lamp is, and the angle it points. Different people were put together differently, and can have different emphases in how they interpret the ultimate goal.</p>
<p>The complexity of <em>Devar Hashem</em> causes the illusion (to us) of paradox. It’s no more real of a paradox than the 5 blind men who argue about the nature of the elephant. The one who felt the elephant’s ear would argue an elephant is like a fan. The one who felt its leg would think it is like a tree. (Google will turn up the story, if you do not know the reference.) But it’s only because we can’t capture the full picture.</p>
<p>We therefore see the Torah as demanding conflicting values and duties. (Unresolvable dialectics, in R YB Soloveitchik-speak.) Depending upon which we choose to prioritize, followers of different <em>derakhim</em> will obtain different results. But you won’t make it to the top of the mountain if you first try this route and that that. You need a consistent plan.</p>
<p>This notion, that <em>halakhah</em> is a model of something far richer, also dovetails well with another idea I fell in love with, something from Professor Moshe Koppel’s book, “Metahalakhah”. There are two ways to learn a language: The native speaker doesn’t learn rules of grammar before using them, he just knows what “sounds right”. In contrast, an immigrant builds his sentences by using formalized rules, learning such terms as “past imperfect” and memorizing the forms that fit each category. R’ Koppel notes that the rules can never perfectly capture the full right vs wrong. A poet has to know when one can take license.</p>
<p>He argues that <em>halakhah</em> is similarly best transmitted by creating “native speakers”. It is only due to loss of our progressive loss of the Sinai culture with each generation that we need to rely on transmitting codified rules. (RMK notes in a footnote the connection between this idea and some ideas in “Rupture and Reconstruction”.) Earlier cited cases are the loss of culture that occurred with Moshe Rabbeinu’s death, when 300 <em>halakhos</em> were forgotten, and Osniel ben Kenaz reestablished them –<em> chazar veyasdum</em>. Similarly the reestablishment of numerous <em>dinim</em> by Anshei Keneses haGedolah after the return from the Babylonian exile — <em>shakhechum vechazar veyasdum</em>. <em>Leyaseid</em>, he suggests, is this codification.</p>
<p>The informal knowledge of a “native speaker” is limited by the capacity of the human mind. But still, it captures more of the ineffable whole, the true “<em>divrei E-lokim Chaim</em>” than can be set down as formal rules.</p>
<p>Even the codified rules, therefore, are not all-or-nothing absolutes. Rather, they give clarity to the issues that a <em>poseiq</em> must weight, highlighting the relevent aspects to different elements of the fuller picture. For example, “<em>acharei rabim lehatos</em>” means that rulings follow the majority. But this doesn’t mean the minority is entirely ignorable; and in fact one may need to rely on that minority opinion if other factors come into play. The <em>poseqi</em> can then weigh pro vs. con.</p>
<p>We’re dealing with a fuzzy system, which acknowledges a realm where answers may be more or less halachic, rather than entirely within or outside the fold. Of course in many situations, the answer is clear and the difference between this kind of system and a straight rule-based algorithm is moot. But those are not the scenarios that require complex <em>pesaqim</em> and become the “interesting cases” in our responsa.</p>
<p>This weight-based methodology doesn’t make for looser requirements. In fact, often quite the opposite. If all rules were absolute, always of the form that factor X always trumps factor Y, then our language for dealing with conflicts in priorities would be quite limited. In cases where conflicts come into play, where the Maharal’s notion of simplification of the Infinite is manifest, one is given no guidelines — and thus full autonomy would have been granted. Rather than an algorithmic interpretation of <em>halakhah </em>being more defining, it’s less.</p>
<p>To explain further by metaphor:<br />
If you have a digital thermostat, it probably is based on Fuzzy Logic. I’m not sure Zadeh’s<br />
“Fuzzy Logic” is the best way to represent more or less vs all or nothing, but it was that meaning that I was suggesting. There are other multi-valued logics. Statistics could even be adapted as one. Quantum Mechanics suggests a third, etc…</p>
<p>Fuzzy Logic is one in which AND means “take the minimum”, and OR means “take the maximum”. Say two balls are different shades of red, one a real primary red — we’ll say it’s .9 red, and another somewhat muddier — just a .2 red. In FL, we would say that the statement “both balls are red” is also a .2, while the statement “at least one of these balls is red” is a .9.</p>
<p>Fuzzy Logic is used in thermostats because the question “is it hot?” really needs to be able to represent “no”, “a little”, “very”, etc… Without such gradations, digital thermostats tend to turn the heat on and off too often (or need some even more complicated solution). Now, one thermostat manufacturer may weigh the heat based on degrees above comfort zone. Another might acknowledge that these things are non-linear, that I’m not nearly half as uncomfortable when the temp is 5 deg off than when it’s 10, and may have some fancier weighting system.</p>
<p>Notice that there are basic rules that any thermostat must comply to. For example, the temperature should be within the desired range at all times. All thermostats will end up sharing certain properties of the rules and the weightings used.</p>
<p>In Artificial Intelligence software, the word “heuristic” is used to describe a system for finding a solution that is less formal than an algorithm, might not always get the optimal solution, but is used because the perfect algorithm either doesn’t exist or would be too slow or complicated to ever get used. In truth, computers are algorithm machines, and thus the heuristic is really a just a much faster or simpler algorithm than one aimed directly at solving the problem perfectly.</p>
<p>Heuristics better represent human thought, as people aren’t algorithm machines. Heuristics better capture that looseness. Like in this case, we weigh pros and cons, not follow strict “IF … THEN …” rules on true vs false prepositions.</p>
<p>And so we find a range of dependence on formal rules in <span style="font-style: italic">teshuvos</span>. There are those I would call <span style="font-style: italic">da’as Torah</span> <span style="font-style: italic">teshuvos</span>, where it’s clear the <span style="font-style: italic">poseiq</span> was enough of a “native speaker” to realize the issues and weigh them before he was even conscious of needing to. The <span style="font-style: italic">teshuvah</span> then becomes an excercise in explaining the ruling post facto, perhaps to confirm than the instinctive answer was sound.</p>
<p>My favorite example of the da’as Torah pesaq is the prohibition of electricity on Shabbos. There is far more universal agreement that electricity just doesn’t fit the feel of Shabbos, as shaped by hours of talmud Torah, than on the reason why it’s assur. And in fact, some of the reasons found are self-evidently stretches to explain after the fact what seemed obvious. <em>Boneh</em> (building) a circuit? Where else do we see something called boneh on Shabbos where there is no actual roof involved?</p>
<p>Then there are the <span style="font-style: italic">teshuvos</span> where the <span style="font-style: italic">poseiq</span> relies very heavily on rules and precedent.</p>
<p>In between are the typical<span style="font-style: italic"> teshuvos</span>, ones where the heuristic nature stands out quite clearly. A common form of <span style="font-style: italic">teshuvah</span> in <span style="font-style: italic">Even haEzer</span> and <span style="font-style: italic">Yoreh Dei’ah</span> (as well as some parts of <span style="font-style: italic">Orakh Chaim</span>, e.g. <span style="font-style: italic">eiruvin</span>) is where the author starts out by proving the law in question is rabbinic, or that some major issue doesn’t apply, and then provide <span style="font-style: italic">snifim lehaqeil</span>, motivations for leniency, where no one is sufficient but the <span style="font-style: italic">poseiq</span> combines them as justification.</p>
<hr align="center" width="33%" />In a future entry, I will explore how this notion is applied differently by various poseqim, and what it means to understanding <em>machloqes</em> and the limits of <em>pesaq</em>. Defining a limit is more difficult when one can’t rely on checking compliance to specific rules. How does one differentiate between differences in prioritization of issues and outright violation of the system?</p><div class="feedflare">
<a href="http://feeds.feedburner.com/~f/Aspaqlaria?a=dPlNQhB"><img src="http://feeds.feedburner.com/~f/Aspaqlaria?i=dPlNQhB" border="0"></img></a> <a href="http://feeds.feedburner.com/~f/Aspaqlaria?a=rZbi7qB"><img src="http://feeds.feedburner.com/~f/Aspaqlaria?i=rZbi7qB" border="0"></img></a>
</div></div>
</td>
</tr>
</table>
<table id="footer" style="border-top:1px solid #999;padding-top:4px;margin-top:1.5em;width:100%" xmlns="http://www.w3.org/1999/xhtml">
<tr>
<td style="text-align:left;font-family:Helvetica,Arial,Sans-Serif;font-size:11px;margin:0 6px 1.2em 0;color:#333;">You are subscribed to email updates from <a href="http://www.aishdas.org/asp">Aspaqlaria</a>
<br>To stop receiving these emails, you may <a href="http://www.feedburner.com/fb/a/emailunsub?id=4187981&key=cQD876uioH">unsubscribe now</a>.</td><td style="font-family:Helvetica,Arial,Sans-Serif;font-size:11px;margin:0 6px 1.2em 0;color:#333;text-align:right;vertical-align:top">Email Delivery powered by FeedBurner</td>
</tr>
<tr xmlns:atom10="http://www.w3.org/2005/Atom">
<td colspan="2" style="text-align:left;font-family:Helvetica,Arial,Sans-Serif;font-size:11px;margin:0 6px 1.2em 0;color:#333;">Inbox too full? <a href="http://feeds.feedburner.com/Aspaqlaria"><img src="http://www.feedburner.com/fb/images/pub/feed-icon16x16.png" style="vertical-align:middle" alt="(feed)"></a> <a href="http://feeds.feedburner.com/Aspaqlaria">Subscribe</a> to the feed version of Aspaqlaria in a feed reader.</td>
</tr>
<tr>
<td style="text-align:left;font-family:Helvetica,Arial,Sans-Serif;font-size:11px;margin:0 6px 1.2em 0;color:#333;" colspan="2">If you prefer to unsubscribe via postal mail, write to: Aspaqlaria, c/o FeedBurner, 20 W Kinzie, 9th Floor, Chicago IL USA 60610</td>
</tr>
</table>
</div>
</body>
</html>