Nedarim 55

Hook

You’re a founder. You’ve just landed that critical seed round. Or maybe you've closed a massive enterprise client. The champagne corks pop, the team celebrates, and then... the lawyers call. Or the VCs. Or your lead engineer. They’re asking about "scope."

"Did we commit to that feature for all tiers?" "Does 'exclusive partnership' mean we can’t even talk to competitors?" "When we promised 'equity compensation,' did that include all future funding rounds, or just this initial grant?"

Suddenly, the clear skies of celebration cloud over with the looming threat of ambiguity. A casual phrase, an unclarified assumption, a term used loosely in a pitch deck or an email — these can evolve from minor misunderstandings into full-blown legal battles, investor disputes, or catastrophic team morale issues. What seemed like a straightforward commitment ("We'll deliver the product by Q4") morphs into a nightmare of "which product?" and "Q4 of which year?"

This isn’t just about legal nitpicking; it's about the very foundation of trust and operational efficiency. Every founder knows the pain of "scope creep" – whether it’s a client demanding features beyond the initial agreement, or an internal team expanding a project far beyond its original mandate. This creep erodes budgets, delays timelines, and saps precious energy. It's a silent killer of startups, often stemming from imprecise language and unexamined assumptions at the moment of commitment.

Consider the classic startup scenario: You promise your early employees "competitive equity." Two years later, a new funding round dilutes everyone significantly, and those early hires feel betrayed. Was "competitive equity" a fixed percentage, or a relative value? What did "equity" even mean – common stock, preferred, options? The intent was good, the language was vague, and now you’re facing a retention crisis. Or, you tell an investor you're building a "platform for X." They hear "comprehensive ecosystem." You mean "MVP with core functionalities." The gap in interpretation can lead to broken trust and future funding roadblocks.

The Talmud, in Nedarim 55, dives deep into the intricate world of vows, exploring the precise meaning of words like "grain," "produce," and "garment." While ancient, these discussions are remarkably relevant to the modern startup. They force us to confront the inherent ambiguity of language and the profound impact of context and intent when making commitments. How broad or narrow is a promise? Who gets to define the boundaries? Is it the speaker's internal thought, the listener's reasonable understanding, or an objective, universally accepted definition? This text is a masterclass in contractual clarity, setting the stage for how we define, communicate, and uphold our commitments, thereby safeguarding our most valuable asset: our reputation and the trust of our stakeholders. Ignore these lessons at your peril; clarity isn't just a nicety, it's an ROI driver.

Text Snapshot

The Mishnah and Gemara in Nedarim 55 delve into the scope of vows using terms like "grain" (dagan), "produce" (tevua), and "crop" (alalta), as well as "garment." A central debate between Rabbi Meir and the Rabbis revolves around whether dagan refers broadly to anything piled like grain or only to the five specific species of grain. The text also highlights Rabbi Yehuda's principle that a vow's scope is "determined according to the one who vows," emphasizing individual intent and context. Finally, it presents a powerful narrative of Rava's initial arrogance and subsequent humility before Rav Yosef, illustrating the personal traits necessary for deep understanding and respectful collaboration.

Analysis

Insight 1: Precision in Definitions & Scope – The ROI of Clarity (Fairness)

The most striking feature of Nedarim 55 is its meticulous examination of linguistic precision. The initial debate over the term "dagan" (grain) is a masterclass in how subtle differences in definition can dramatically alter the scope of a commitment. Rabbi Meir argues that if one vows to refrain from dagan, it "is prohibited to eat the dry cowpea, because, like grain, its final stage of production involves being placed in a pile." His reasoning, as explained by the Ran, is that "since it is piled like grain, Rabbi Meir holds it is called dagan." The Shita Mekubetzet further clarifies Rabbi Meir's approach, noting that he "sber l'lashon bnei adam" – he follows "common human usage" for the term dagan, which would include anything gathered into a heap. In contrast, "the Rabbis say: It is prohibited for him to partake of only the five species of grain: Wheat, barley, oats, spelt, and rye, as that is the connotation of the term dagan in the Torah." (Nedarim 55a:1). Rashi explicitly lists these five species, providing the narrow, canonical definition. The Rabbis, according to the Shita Mekubetzet, "l'lashon Torah nitkaven" – they intend for the term to be understood according to its usage in the Torah, which is more specific.

This isn't an academic squabble; it's a foundational lesson for any founder. Every term in your pitch deck, your term sheet, your employee contracts, or your customer agreements carries a potential for multiple interpretations. Is "AI-powered" a commitment to a specific algorithmic sophistication, or just a marketing buzzword? Does "data security" mean compliance with a specific framework like ISO 27001, or a general commitment to safeguard information? The Rabbis represent the "statutory" or "canonical" interpretation, advocating for a narrow, well-defined scope based on established definitions. Rabbi Meir, on the other hand, leans into "common usage" – how people generally understand the term, which can be broader and more contextual.

The Gemara further complicates this with the introduction of "tevua" and "alalta." Rabbi Meir differentiates between dagan (broad, piled items) and tevua (specifically the five species), as Rashi clarifies: "I definitely agree that one who vows from tevua is only forbidden from the five species, but one who vows from dagan is forbidden from any type that is piled." (Rashi on Nedarim 55a:1:2). Then, Rava sends a query to Rav Yosef about "alalta" (crop). Rav Yosef initially equates it to tevua, meaning the five species. But Abaye strongly objects: "Are the two cases comparable? Although tevua means grain and includes only the five species, alalta means crop and includes all items that grow." (Nedarim 55a:10). The very fact that Rava, a great scholar, had to send this question underscores the real-world ambiguity of terms.

Startup Case Study: SaaS Feature Scope

Imagine a startup, "CloudVault," offering secure cloud storage. Their initial contract with an enterprise client, "GlobalCorp," states that CloudVault will provide "advanced data management capabilities." CloudVault's engineering team interprets this narrowly, focusing on robust encryption, version control, and basic access logs (the "five species" of data management). GlobalCorp, however, interprets "advanced data management" much more broadly, expecting sophisticated AI-driven anomaly detection, automated compliance reporting for various global regulations, and multi-cloud integration (the "all items that grow" interpretation, like alalta).

This divergence stems directly from the dagan debate. CloudVault, like the Rabbis, relied on a canonical, technical definition. GlobalCorp, like Rabbi Meir, used a more colloquial, aspirational understanding. The result: massive scope creep, missed expectations, budget overruns, and a strained client relationship. CloudVault finds itself having to build features it never budgeted for, or risk losing a crucial client.

The ROI of clarity here is immense. Had CloudVault explicitly defined "advanced data management capabilities" in an appendix, specifying the exact features included (or excluded), this conflict could have been avoided. This involves being proactive, like Abaye distinguishing tevua from alalta. It's not enough to use a common term; you must define your common term.

KPI Proxy: "Scope Creep Index" (SCI). This can be measured as the percentage of additional features or functionalities requested by a client (or added internally) beyond the initial, formally documented agreement, weighted by their development cost/time. A high SCI indicates a failure in initial definitional clarity. For instance, if the initial agreement specified 10 core features, and 5 additional, significant features were added during the project, the SCI would be 50%. A healthy SCI should be as close to 0% as possible.

Insight 2: Intent vs. Literal Language – The Human Element in Commitments (Truth)

While precision in definitions is crucial, Nedarim 55 also acknowledges that language is not always a perfect mirror of intent. Sometimes, the spirit of the commitment, or the specific context in which it was made, should override a purely literal interpretation. This is encapsulated in Rabbi Yehuda's profound principle: "Everything is determined according to the one who vows." (Nedarim 55a:17).

The Gemara illustrates this with two compelling examples regarding vows about "wool" and "linen." If "one was bearing a burden of wool and linen, and was sweating, and its smell was unpleasant for him, and in reaction, he said: Wool and linen are konam for me and I will therefore not place them upon myself," Rabbi Yehuda rules that "it is permitted for him to cover himself with wool and linen garments, but it is prohibited for him to sling them over his shoulder behind him as a burden." (Nedarim 55a:17). Why? Because the circumstances of his vow – the discomfort of carrying the burden – clearly indicate his intent was to avoid carrying, not wearing. Conversely, if "one was wearing a woolen garment and it caused him discomfort, and in reaction he said: Wool is konam for me, and I will therefore not place it upon myself, it is prohibited for him to wear woolen garments, but it is permitted to place a burden of woolen garments upon him." (Nedarim 55a:21). Here, the discomfort from wearing the garment dictates the scope of the prohibition.

This principle is revolutionary because it moves beyond mere lexical definitions (like the dagan debate) to consider the subjective experience and motivation of the person making the commitment. The Rosh, in his commentary on a related passage about vows related to "this year," supports this idea by noting that in nedarim (vows), "halakh acharei lashon bnei adam" – one follows "common human usage" and the natural understanding of the speaker, even when it pertains to calendar years and leap years. If someone says "this year," they intend a full year as commonly understood, even if it becomes a leap year, because "l'tza'arei nafshia kabil aleha v'ha itza'er" – "they accepted upon themselves to suffer, and they have suffered" (Rosh on Nedarim 8:2:1). The implication is that the intent to undertake a burden, rather than a narrow legalistic reading, defines the scope.

For founders, this means understanding that agreements are not just static documents; they are living reflections of human intent, made in specific contexts. While written contracts aim for objective clarity, the underlying truth often lies in the shared (or unshared) understanding at the moment of agreement.

Startup Case Study: Employee Stock Options and Vesting

Consider a startup, "InnovateTech," that promises "accelerated vesting" to a key early engineer, Sarah, to incentivize her crucial early contributions. The written stock option agreement states a standard 4-year vesting schedule with a 1-year cliff, and then a clause about "accelerated vesting upon a change of control event." Sarah, however, understood "accelerated vesting" in the context of her initial negotiation – a verbal promise from the founder that if she hit certain performance milestones, her vesting schedule would be sped up regardless of a change of control. She believed the written agreement would reflect this broader intent, even if the specific language wasn't perfectly aligned.

When InnovateTech is acquired two years later, Sarah's options only partially vest based on the "change of control" clause. The founder, honestly, had forgotten the nuance of their earlier conversation and believed the written contract was the final word. Sarah feels betrayed. The founder, like the one who vowed about wool, had a specific intent at the moment of the verbal promise (to reward performance), but the literal language of the contract didn't fully capture it. Rabbi Yehuda would compel us to look at the context and intent of the original verbal agreement, not just the later, more formal (and potentially less comprehensive) written terms.

Fairness here demands recognizing that the spirit of the commitment, especially when it influences critical career decisions, should hold significant weight. A company that consistently prioritizes the narrowest literal interpretation over clear, albeit unwritten, intent risks a reputation for being unfair and litigious, leading to high employee turnover and difficulty attracting top talent.

KPI Proxy: "Employee Clarification Requests (ECR) per Policy." This metric tracks how many times employees seek clarification on internal policies, benefits, or compensation terms. A high ECR suggests ambiguity in communication or a mismatch between the perceived intent of a policy and its literal interpretation, indicating a need for better alignment and transparency. This metric measures the trust gap.

Insight 3: The Danger of Arrogance and the Value of Humility – Collaborative Success (Competition/Collaboration)

Beyond the legalistic discussions of vows, Nedarim 55 offers a profound ethical lesson on leadership, collaboration, and the pursuit of knowledge through the interaction between Rava and Rav Yosef. This narrative is a powerful commentary on the personal qualities that enable or hinder effective decision-making and collaborative success.

Rava, a brilliant scholar, initially sends a question to his teacher, Rav Yosef, regarding the definition of "alalta" (crop). Rav Yosef responds, equating it to tevua (the five species). However, upon receiving the answer, Rava dismisses it: "He said: That was not a dilemma for me, i.e., the fact that alalta means all items that grow. This is the matter that is a dilemma for me: What is the legal status of profits from the rent of houses and the rent of boats?" (Nedarim 55a:11). Rava's reaction, relayed to Rav Yosef, sparks anger in his teacher: "Rav Yosef said: And since he does not need us, and he believes that he knows the answer himself, why did he send us the question? Rav Yosef became angry with Rava." (Nedarim 55a:12).

This episode is a stark warning against intellectual arrogance and the disrespect it breeds. Rava, despite his brilliance, undermined his teacher's authority and wasted his time by sending a question he seemingly already knew the answer to, only to then pivot to a new question without acknowledging the prior response. Such behavior can cripple collaboration in any organization.

The turning point comes when Rava, realizing his error, seeks to appease Rav Yosef on Yom Kippur eve. His act of humility – quietly diluting wine for his blind teacher, an act that Rav Yosef recognized as Rava's due to its distinct character – opens the door for reconciliation. Rava then offers a profound interpretation of the verse "And from the wilderness Mattana and from Mattana Nahaliel..." (Numbers 21:18–19). His explanation emphasizes that "Once a person renders himself like a wilderness, deserted before all, the Torah is given to him as a gift [mattana]... And if he elevates himself and is arrogant about his Torah, the Holy One, Blessed be He, degrades him... And if he reverses his arrogance and becomes humble, the Holy One, Blessed be He, elevates him..." (Nedarim 55a:15). This eloquent exposition on humility and its link to receiving wisdom serves as Rava's sincere apology and demonstration of changed character.

For founders, this story is vital for understanding the dynamics of leadership, team building, and competitive strategy. Arrogance, whether directed internally at team members or externally at competitors and partners, is a destructive force. A founder who believes they have all the answers, dismisses expert advice, or treats collaborative efforts as opportunities to showcase their own brilliance rather than genuinely seeking input, will inevitably alienate talent, miss critical insights, and undermine their company's long-term viability. The "wilderness" analogy speaks to the necessity of emptying oneself of ego to truly receive and process new information – a prerequisite for innovation.

Startup Case Study: Founder Hubris in Product Development

Consider "InnovateNow," a tech startup with a brilliant but notoriously arrogant founder, Alex. Alex believes his vision is infallible. During product development, the engineering team, after extensive market research and technical feasibility studies, advises against implementing a complex, niche feature that Alex insists upon. They present data showing low user demand, high development cost, and significant technical debt. Alex, like Rava initially, dismisses their concerns, essentially saying, "That's not the real problem; I already know the solution." He forces the team to build the feature, ignoring their expertise and essentially asking them to "send him questions" whose answers he already believed he possessed.

The result is devastating. The feature consumes a disproportionate amount of resources, delays the launch of more critical functionalities, and ultimately fails to gain traction. The engineering team becomes demoralized, feeling unheard and disrespected. Key talent leaves, citing a "toxic culture of hubris." InnovateNow, once a promising startup, struggles to recover, its reputation tarnished not by lack of talent, but by a failure of leadership rooted in arrogance.

A founder who embraces the lesson of Rava's humility, who genuinely seeks counsel, listens to dissenting opinions, and acknowledges when they might be wrong, fosters a culture of psychological safety where good ideas can flourish, regardless of their source. This humility allows for adaptation, learning from mistakes, and ultimately, more resilient and successful competition.

KPI Proxy: "Inter-team Collaboration Score." This can be measured through anonymous internal surveys, asking employees to rate the effectiveness of collaboration between different departments (e.g., engineering and product, sales and marketing), the openness of leadership to feedback, and the perceived value placed on diverse perspectives. A low score indicates a siloed, potentially arrogant culture where ideas are not flowing freely or respectfully. This can be directly linked to product innovation and market responsiveness.

Policy Move

The "Commitment Clarity & Intent Protocol"

Based on the insights from Nedarim 55, especially the distinction between precise definitions and the critical role of intent, I propose implementing a "Commitment Clarity & Intent Protocol" for all significant internal and external agreements. This protocol aims to mitigate ambiguity, foster trust, and reduce costly disputes by ensuring that every commitment is thoroughly defined and understood by all parties.

The core problem Nedarim 55 highlights is the gap between the literal meaning of a term and the intended scope in a specific context. Rabbi Meir and the Rabbis clash over the definition of dagan, while Rabbi Yehuda emphasizes the vower's intent. Without a clear process, a company is vulnerable to this definitional drift and subjective interpretation, leading to friction with customers, investors, and employees.

Sample Policy Draft:

Policy Name: Commitment Clarity & Intent Protocol (CCIP) Effective Date: [Date] Owner: Legal Department / Head of Operations Scope: All new contracts, partnership agreements, investment documents, significant internal policy changes (e.g., compensation, benefits), and major product roadmap commitments (features, timelines).

1. Definitional Precision (Drawing from dagan debate): * 1.1. Explicit Definitions: For every key term or deliverable within a commitment, define it explicitly in writing. Avoid relying solely on common usage where ambiguity is possible. * Example: If a term sheet mentions "liquidation preference," define the exact multiplier and whether it's participating or non-participating. If a product feature is "AI-powered," specify the type of AI (e.g., machine learning, natural language processing) and its specific function within the feature. * 1.2. Scope Delimitation: Clearly delineate what is included and, crucially, what is excluded from the scope of the commitment. This preempts "scope creep." * Example: "The 'Advanced Analytics Dashboard' includes real-time data visualization and historical trend analysis for sales metrics. It explicitly excludes predictive modeling or integration with third-party CRM systems, which would be separate SOWs." This mirrors Abaye's distinction between tevua and alalta – clarifying what falls into "the five species" versus "all items that grow." * 1.3. Glossary of Terms: Maintain a centralized, accessible glossary of commonly used internal and external terms with their agreed-upon definitions. This serves as the company's "canonical" interpretation, akin to the Rabbis' adherence to the Torah's definition of dagan.

2. Intent Alignment & Documentation (Drawing from Rabbi Yehuda's principle): * 2.1. Statement of Intent: For every significant commitment, include a "Statement of Intent" section. This brief narrative explains the underlying purpose, context, and mutual understanding of the parties at the time the commitment is made. * Example: In an employee equity grant: "The intent of this 'Early Contributor Equity Grant' is to recognize outstanding foundational contributions and to incentivize long-term commitment to the company's mission, beyond standard compensation." This provides the "why" behind the "what," reflecting Rabbi Yehuda's focus on the vower's context. * 2.2. Stakeholder Confirmation: Before finalization, require explicit confirmation (e.g., sign-off, recorded meeting minutes) from all primary stakeholders that they understand both the literal terms and the stated intent. Document any discrepancies or questions raised during this process. This prevents Rava's initial dismissal of Rav Yosef's answer by ensuring all parties are genuinely aligned. * 2.3. Scenario Planning (Optional but Recommended): For high-stakes commitments, brainstorm potential future scenarios (e.g., acquisition, market shift, key personnel departure) and discuss how the commitment's terms and intent would apply. Document these discussions.

3. Review and Update Cycle: * 3.1. Regular Review: Schedule periodic reviews (e.g., annually, or upon major company milestones) for all active commitments to ensure continued alignment between terms, intent, and evolving circumstances. * 3.2. Amendment Process: Establish a clear, documented process for amending commitments, requiring re-affirmation of both precise terms and updated intent from all parties.

Implementation Steps:

1. Pilot Program: Start with a pilot group (e.g., one department or specific type of contract) to test the protocol, gather feedback, and refine the process.
2. Training & Education: Conduct mandatory training for all relevant personnel (e.g., sales, HR, legal, product managers, founders) on the CCIP, emphasizing the why (risk mitigation, trust building) behind the what. Use real-world company examples to illustrate the costs of ambiguity.
3. Tooling Integration: Integrate CCIP requirements into existing tools (e.g., CRM for contract generation, HRIS for policy documentation, project management software for feature definitions). Create templates that prompt for explicit definitions and statements of intent.
4. Ownership & Accountability: Clearly assign ownership for protocol adherence within each department or for specific types of agreements. The Legal or Operations department should oversee the overall implementation and auditing.
5. Communication Campaign: Launch an internal campaign emphasizing the value of clarity, linking it to company values like integrity and efficiency.

Potential Pushback and How to Address It:

1. "Too much bureaucracy, slows us down."
   • Response: Frame it as "pre-emptive problem-solving." Highlight past instances where ambiguity led to delays, rework, or legal costs. "A few extra hours upfront for clarity can save weeks or months of remediation later. This isn't bureaucracy; it's robust risk management and trust-building, directly impacting our velocity and reputation." The cost of not defining dagan clearly can be significant.
2. "It's impossible to define everything; some things are implicit."
   • Response: Acknowledge that perfection is unattainable, but progress is essential. "The goal isn't to define every single nuance, but to address the high-impact areas where ambiguity historically creates friction. Rabbi Yehuda's wisdom teaches us that intent matters, but it's our responsibility to make that intent as explicit as possible." Focus on "material terms" and "critical deliverables."
3. "Clients/partners won't agree to such detailed definitions; they want flexibility."
   • Response: Reframe it as protecting their interests too. "Clarity protects both parties. We can present this as a commitment to transparency and mutual understanding, ensuring that their expectations are precisely met, and that we avoid surprises down the line. It builds long-term trust." The Rashba's discussion on what form of dagan is forbidden (raw vs. processed) highlights how even a slight change in form can shift the meaning; this level of detail can be offered as a benefit to the partner.
4. "We trust our people; we don't need to over-document intent."
   • Response: "Trust is paramount, but memory fades, people move on, and contexts change. This protocol isn't about lack of trust; it's about building a durable, institutional memory of our commitments. It ensures that even as our team evolves, the foundational understanding of our agreements remains intact, preventing future Rava-Rav Yosef style misunderstandings and anger." This also helps new hires understand the spirit of existing agreements.

This protocol, by systematizing the lessons of Nedarim 55, transforms abstract ethical principles into actionable business processes, directly impacting efficiency, reputation, and ultimately, the bottom line.

Board-Level Question

"Given the potential for ambiguity in language and the critical role of intent in our agreements, how are we systematically ensuring that our core commitments – to customers, employees, and partners – are interpreted consistently and fairly, aligning both literal terms and underlying purpose across the organization?"

This question cuts to the heart of operational integrity and strategic alignment, drawing directly from the core insights of Nedarim 55. The text vividly illustrates how the imprecise use of terms like dagan, tevua, and alalta can lead to conflicting interpretations and unintended obligations. The debate between Rabbi Meir and the Rabbis regarding the scope of dagan – one favoring common usage, the other a strict canonical definition – mirrors the tension between a flexible, colloquial approach to commitments and a rigid, literal one. At the board level, this translates into asking whether the company is systematically closing this interpretive gap, or if it's leaving critical relationships vulnerable to misinterpretations that could lead to costly disputes, damaged reputation, or internal strife.

Furthermore, Rabbi Yehuda's principle that "everything is determined according to the one who vows" highlights the profound importance of intent and context alongside literal language. A founder's initial promise to an early employee, or a verbal agreement with a key partner, may carry a specific unwritten intent that the formal documentation later fails to capture fully. The board needs to understand how the company balances the necessity of clear, written terms with the ethical imperative to honor the spirit of its commitments, especially when circumstances change or personnel turn over. Are we fostering a culture where the underlying purpose of an agreement is remembered and respected, or are we defaulting to the narrowest possible legalistic interpretation, risking morale and trust?

The Rava-Rav Yosef narrative adds another layer, emphasizing the ethical leadership required to navigate these ambiguities. Rava's initial arrogance in dismissing his teacher's answer, and his subsequent humility, underscore the personal qualities that enable effective collaboration and problem-solving. A board must consider if the leadership team, and the company culture as a whole, embodies the humility necessary to acknowledge ambiguity, seek clarification, and engage in open dialogue rather than defaulting to unilateral interpretations. How does the company ensure that critical questions about scope, intent, and definition are not met with dismissiveness, but with a genuine desire for shared understanding and fairness, ultimately impacting the company's ability to innovate, retain talent, and build lasting relationships in a competitive market? The answer to this strategic question dictates not just compliance, but the very character and long-term viability of the enterprise.

Takeaway + Citations

The intricate discussions in Nedarim 55 reveal that language is rarely as precise as we assume, and commitments carry layers of literal meaning, contextual intent, and underlying purpose. For founders, this translates into an imperative for radical clarity in all agreements – defining terms explicitly like the Rabbis, but also understanding and documenting the spirit and context of those commitments, as taught by Rabbi Yehuda. Furthermore, the narrative of Rava's arrogance and humility underscores that true wisdom and effective collaboration stem from a posture of openness, respect, and a willingness to learn, rather than from ego. Prioritizing definitional precision, aligning intent, and cultivating humility are not just ethical virtues; they are critical business strategies that minimize risk, build trust, and drive sustainable growth.

Citations

• Nedarim 55a:1: https://www.sefaria.org/Nedarim.55a.1?lang=en&with=all&lang2=en
• Nedarim 55a:3: https://www.sefaria.org/Nedarim.55a.3?lang=en&with=all&lang2=en
• Nedarim 55a:10: https://www.sefaria.org/Nedarim.55a.10?lang=en&with=all&lang2=en
• Nedarim 55a:11: https://www.sefaria.org/Nedarim.55a.11?lang=en&with=all&lang2=en
• Nedarim 55a:12: https://www.sefaria.org/Nedarim.55a.12?lang=en&with=all&lang2=en
• Nedarim 55a:13: https://www.sefaria.org/Nedarim.55a.13?lang=en&with=all&lang2=en
• Nedarim 55a:15: https://www.sefaria.org/Nedarim.55a.15?lang=en&with=all&lang2=en
• Nedarim 55a:17: https://www.sefaria.org/Nedarim.55a.17?lang=en&with=all&lang2=en
• Nedarim 55a:21: https://www.sefaria.org/Nedarim.55a.21?lang=en&with=all&lang2=en
• Rosh on Nedarim 8:2:1: https://www.sefaria.org/Rosh_on_Nedarim.8.2.1?lang=en&with=all&lang2=en
• Ran on Nedarim 55a:1:1: https://www.sefaria.org/Ran_on_Nedarim.55a.1.1?lang=en&with=all&lang2=en
• Rashi on Nedarim 55a:1:1: https://www.sefaria.org/Rashi_on_Nedarim.55a.1.1?lang=en&with=all&lang2=en
• Rashi on Nedarim 55a:1:2: https://www.sefaria.org/Rashi_on_Nedarim.55a.1.2?lang=en&with=all&lang2=en
• Shita Mekubetzet on Nedarim 55a:1: https://www.sefaria.org/Shita_Mekubbetzet_on_Nedarim.55a.1?lang=en&with=all&lang2=en