“Covenant and Kindness” Parashat Ekev 5786
The Portion of Ekev opens with a promise that is easy to overlook but difficult to explain. [Devarim 7:12]: “If you listen to these laws and observe them carefully, then G-d will keep for you the covenant and the kindness that He swore to your forefathers”. Why does the Torah distinguish between “covenant” and “kindness”? Aren’t they simply two ways of describing G-d’s faithfulness? I suggest that the Torah is making a subtle but profound distinction: A covenant is built on well-defined obligations, boundaries, and expectations. Without clear terms and conditions, there can be no covenant. Kindness, on the other hand, operates in an entirely different realm. Kindness begins where obligation ends. Kindness is voluntary rather than compulsory. It is the decision to do more than justice requires. No one has ever been criticized for being “too kind”. The Torah therefore presents Judaism as resting on two complementary pillars. The covenant establishes what must be done, while kindness inspires us to go beyond what is required. The challenge is recognizing that the two are not interchangeable. The wording of the verse makes the question even sharper. The Torah speaks of “the covenant and the kindness that He swore to your forefathers.” The reference to an oath seems natural when applied to a covenant. A covenant is a binding commitment and an oath reinforces that commitment. But how can one swear himself to kindness? Kindness, by definition, cannot be compelled. The moment it becomes an obligation, it is no longer kindness. I suggest that the Torah is deliberately referring to two fundamentally different dimensions of the relationship between G-d and the Jewish People. The covenant consists of commitments that are fixed and inviolable. The kindness refers not to obligations but to the willingness to go beyond them. The Torah introduces two distinct categories whose boundaries must never be confused.
This distinction sheds new light on an earlier commandment in the Portion of Va’etchanan [Devarim 4:2]: “You shall not add to the word that I command you, nor shall you subtract from it”. At first glance, the prohibition appears perfectly symmetrical. Adding and subtracting seem equally forbidden. Rabbi Baruch HaLevi Epstein[1], writing in Tosefet Berachah, offers a fascinating perspective. The real danger is not the additional act itself. Suppose someone paid extra and purchased, along with his lulav set, a prune and a mangosteen. The extra fruits are halachically meaningless. The physical act of doing more than commanded is not what threatens the Torah. The greater danger is what that addition implies. Once people convince themselves that they may improve G-d’s commandments by adding to them, they have also accepted the premise that the commandments are subject to human modification. If they can add, they can also subtract. Today’s addition becomes tomorrow’s omission. The prohibition against adding exists because it ultimately protects against subtracting. The Torah is less concerned with arithmetic than with preserving the integrity of the covenant.
Engineers often encounter problems of this sort in system design. Every successful project begins with a requirements specification that defines not only what the system should do but also what it is not intended to do. Good engineers constantly make systems more robust. They add redundancy, safety margins, fault tolerance, and graceful failure modes. None of these additions changes the original specification. They simply help the system achieve its intended purpose more reliably. But engineers also fear another phenomenon, called “feature creep”. One stakeholder requests an additional capability, another suggests a seemingly minor enhancement, and another proposes one more improvement. Each addition in and of itself appears reasonable, yet over time the product drifts further and further from its original mission. Complexity increases, reliability suffers, and eventually no one remembers what the system was originally designed to accomplish. The problem is not that there are too many features. The problem is that the specification has quietly drowned.
The movie “Pentagon Wars[2]” offers a memorable satire of precisely this kind of phenomenon. The “Bradley Fighting Vehicle” began with a clear and focused mission as a mechanized infantry combat vehicle, but as the program progressed, different constituencies demanded additional capabilities. One group wanted greater firepower. Another insisted on heavier armour. Others sought reconnaissance equipment, amphibious capability, or protection against emerging threats. Each request appeared reasonable when viewed on its own. Each promised to make the vehicle more capable and more useful. The problem was that these additions did not occur in isolation. More armour added weight. More weight reduced mobility. Reduced mobility required a larger engine. New equipment competed for space with troops and supplies. Every enhancement solved one problem while creating several others. The vehicle that emerged after years of modifications still bore the name “Bradley,” but it had drifted far from the original concept. The humour of “Pentagon Wars” comes from watching intelligent, well-meaning professionals[3] create a system that becomes increasingly complex as they attempt to satisfy competing objectives.
The lesson extends far beyond military procurement. Most complex systems do not lose their effectiveness because of one single bad decision. They lose their effectiveness gradually. A successful design attracts new users, new stakeholders, and new requirements. Every proposed feature is supported by a persuasive argument and a legitimate use case. Yet the cumulative effect can be transformative. A system loses its identity not because someone makes one bad decision, but because countless well-intentioned additions gradually replace the original design. The central challenge of engineering leadership is therefore not simply to add capability, but to preserve purpose. Knowing what to exclude is often as important as knowing what to include.
This brings us back to the opening verse of the Portion of Ekev. G-d promises to preserve both the “covenant” and the “kindness” because they belong to two different domains. The covenant defines our obligations. Kindness determines how generously, compassionately, and wholeheartedly we fulfill them. The covenant commands us to give charity; kindness determines how much we give. The covenant commands us to visit the sick; kindness determines how long we remain at the bedside. The covenant commands hospitality; kindness determines the warmth with which we welcome our guests. Human creativity belongs not in rewriting G-d’s commandments but in expanding our response to them. The Torah never discourages us from doing more. It simply teaches that “more” belongs in the realm of kindness rather than in redefining the covenant itself.
G-d can swear to preserve the covenant because a covenant is defined by fixed commitments. He can also promise kindness because He pledges not merely to fulfill His obligations, but to relate to the Jewish People with generosity that transcends obligation. Our task is to mirror that relationship. We preserve the covenant exactly as it was given, resisting the temptation to redefine it through either addition or subtraction. At the same time, we are called to express limitless kindness within the framework of that covenant. The guardrails of halacha are not obstacles to spiritual growth. They are what make genuine growth possible. The covenant gives our service its structure. Kindness gives it its soul. Only when we preserve the distinction between the two do we remain faithful to both.
Shabbat Shalom,
Ari Sacher, Moreshet, 5786
Please daven for a Refu’a Shelema for Rachel bat Malka, Iris bat Chana, Sheindel Devora bat Rina, Esther Sharon bat Chana Raizel, Meir ben Drora, Golan ben Marcelle and Hodayah Emunah bat Shoshana Rachel.
[1] Rabbi Epstein, often called after his main commentary on the Torah, “Torah Temima”, lived in Belarus about 150 years ago. “Tosefet Bracha” was the go-to commentary of my Rebbe, Rabbi Silberrman.
[2] “Pentagon Wars” is available on YouTube. It is a must-watch for any beginning engineer.
[3] Using taxpayer dollars
