Daily Rambam · Startup Mensch · Standard
Mishneh Torah, Eruvin 2
Hook
You are closing a critical Series B round. The lead investor is ready to wire $15 million. The term sheet is signed, the legal fees are racking up, and the board is aligned. Then, you hit a brick wall. A legacy angel investor from your pre-seed days, who owns a mere 1.2% of the company on a safe note that converted under legacy terms, refuses to sign the drag-along agreement. They aren’t even demanding more money; they are simply unresponsive, vacationing in a remote corner of the world without cell service, or perhaps nursing an old grievance about a pivot you made three years ago.
Your entire enterprise is paralyzed. The lead investor refuses to close until there is 100% clean capitalization table sign-off. This is the "holdout problem"—the high-stakes reality where a single non-cooperative stakeholder can veto the collective progress of an entire ecosystem.
In corporate governance, we often assume that majority rules. In reality, veto points, passive-aggressive non-participation, and operational friction can freeze your company’s velocity just as effectively as a court injunction.
The ancient Rabbis understood this systemic vulnerability intimately. In the laws of the eruv—the legal fiction that merges individual private domains into a single collective domain to permit carrying on the Sabbath—they confronted the exact same structural design flaw. If a single resident of a shared courtyard refuses to participate in the communal eruv, or simply forgets to join, their non-participation paralyzes the entire community. Under rabbinic law, no one in that courtyard can carry items from their homes to the shared space.
But the Talmudic sages were not bureaucrats; they were operational pragmatists. They did not allow a single holdout to permanently freeze the community's economic and physical mobility. Instead, they engineered legal release valves: Bitul Reshut (the subordination of domain) and Sechirat Reshut (the rental of domain).
This text is a masterclass in governance architecture. It teaches founders how to design contracts, structure cap tables, and negotiate partnerships so that a single unaligned actor cannot veto your company’s destiny. If you want to build a highly collaborative, high-velocity business without being held hostage by minority stakeholders, you must master the mechanics of domain subordination.
Full Experience in the App
Listen. Chat. Go deeper.
Audio playback, interactive chevruta, Hebrew tools, and every daily learning track — only in Derekh Learning.
Text Snapshot
"When all the inhabitants of a courtyard, with one exception, have established an eruv, this individual [causes carrying] to be forbidden... Should the person who did not join in the eruv subordinate the ownership of merely [his share] of the courtyard [to the others], they are permitted to carry from their homes to the courtyard and from the courtyard to their homes... When a person subordinates the ownership of his domain, he must make an explicit statement to that effect to every inhabitant of the courtyard, saying, 'My domain is subordinated to you, and to you, and to you.'" — Mishneh Torah, Eruvin 2:1-2
Analysis
To build a resilient enterprise, a founder must distinguish between different classes of stakeholders and design specific mechanisms to manage their alignment. The Rambam’s analysis of eruv and domain subordination yields three powerful decision rules for modern business leadership.
Insight 1: The Architecture of Subordination (Bitul Reshut) — Fairness in Veto Mitigation
The fundamental dilemma of the courtyard is that a single non-participant halts all spatial transition. The Rambam writes:
"this individual [causes carrying] to be forbidden" Mishneh Torah, Eruvin 2:1.
To solve this without forcibly expropriating the holdout’s property, the Sages created Bitul Reshut (subordination of domain).
As Rabbi Adin Steinsaltz notes in his commentary on Mishneh Torah, Eruvin 2:1:1:
"בִּטֵּל לָהֶן זֶה שֶׁלֹּא עֵרֵב רְשׁוּת . ועל ידי כך העביר להם את רשותו ומותרים לטלטל" (He subordinated his domain to them, and through this, he transferred his authority to them, and they are permitted to carry).
This is not a permanent transfer of equity or title; it is a temporary, functional waiver of veto power. In modern venture-backed startups, this is the exact legal theory behind drag-along rights, voting proxies, and information rights waivers.
When you onboard early-stage angels, advisors, or minor co-founders, you must build "subordination of domain" directly into your corporate charter. You cannot afford to run a democratic town hall for every operational pivot or capital raise. If an investor's shareholding falls below a certain threshold (e.g., 5%), their voting rights must automatically subordinate to the Board of Directors or the majority of common stock.
The Decision Rule
Do not permit passive equity to retain active veto rights. If a stakeholder does not actively contribute to the operational velocity of the company (the "carrying of articles"), their governance rights must be structured such that they can be unilaterally subordinated (bitul) under predefined conditions (e.g., a qualified financing round or a majority-approved sale). You protect their economic rights (their "house"), but you strip their ability to paralyze the common space (the "courtyard").
Insight 2: Sincerity and Behavioral Alignment (Maintain Commitment) — The Truth of Operational Relinquishment
Subordination is not merely a paper transaction; it requires behavioral integrity. The Rambam rules:
"If he willingly transfers the article, his act causes the others to be forbidden, for he did not maintain his commitment" Mishneh Torah, Eruvin 2:5.
If a resident subordinates his domain but then acts as if he still owns it by carrying his own items into the courtyard, he nullifies the subordination. His actions expose his verbal waiver as a sham.
In business, this speaks directly to the painful process of founder transitions and executive departures. When a co-founder steps down from an active operational role to a passive board seat or advisory position, they are "subordinating their domain." They have agreed to let the remaining executive team run the courtyard.
However, if that departed founder continues to backchannel with engineering leads, critique product roadmaps on public Slack channels, or seed doubt among early employees, they are "willingly transferring the article." They are acting like an active owner while claiming to be a passive observer. This behavioral contradiction destroys the operational alignment of the company, paralyzing the team's execution.
As the Shulchan Aruch HaRav notes, the reason this behavior nullifies the subordination is that:
"the person's act shows that his commitment was not genuine at the outset."
If the transition is not genuine, the organization is left in a state of suspended animation—partially managed by the new leadership, partially sabotaged by the old.
The Decision Rule
When a leader or major stakeholder steps back, their operational access must be cleanly severed to prevent structural interference. Sincerity in corporate transitions cannot rely on goodwill alone; it must be enforced by operational boundaries (e.g., revoking GitHub access, removing them from operational Slack workspaces, and defining strict non-interference covenants in their separation agreement). If they "carry" in your courtyard after subordinating their domain, they invalidate the transition and freeze your team.
Insight 3: Transactional Coexistence with External Stakeholders (Sechirat Reshut) — Competition and the Nominal Contract
The Rambam introduces a stark difference when dealing with a non-Jewish neighbor in the courtyard:
"For an eruv may not be established where a gentile is present, nor is the subordination of one's domain effective when a gentile is present. There is no alternative other than renting the gentile's domain" Mishneh Torah, Eruvin 2:10.
Because the external neighbor does not share the same covenantal or religious obligations, the internal, trust-based mechanism of Bitul Reshut (subordination) is legally invalid. You cannot ask an outsider to "spiritually waive" a domain they do not recognize as spiritually bound. Instead, you must use a cold, transactional mechanism: commercial rental (sechirat reshut), even if it is for a nominal fee of "less than the value of a prutah" Mishneh Torah, Eruvin 2:11.
This is a profound lesson in stakeholder segmentation. In any business ecosystem, you have two distinct classes of actors:
- Internal Covenantal Partners: Founders, employees, and core investors who share the long-term vision, cultural values, and upside of the enterprise. You can align with them through equity, trust, and mutual subordination of interests (bitul).
- External Transactional Partners: Vendors, landlords, independent contractors, and legacy competitors. They do not care about your mission; they care about their balance sheet.
You cannot manage external partners with internal culture. You cannot ask a software vendor or a landlord to "subordinate their interests" for the good of your startup's mission. When dealing with them, you must use formal, transactional contracts.
Moreover, the Rambam notes that if there are multiple external parties, you must account for every single one:
"If many gentiles are present, they must rent their domains to the Jews" Mishneh Torah, Eruvin 2:10.
The Ohr Sameach on Ohr Sameach on Mishneh Torah, Eruvin 2:10:1 highlights this rigor, citing the Jerusalem Talmud:
"עשרה גוים שהיו דרין בבית אחד צריך לשכור מכולם" (Ten gentiles dwelling in one house require renting from all of them).
Furthermore, the Rambam insists that you cannot bypass this by having the internal partners simply consolidate their power to ignore the outsider:
"Similarly, if they subordinate the ownership of their domain to the gentile... or one of the Jews subordinates the ownership of his domain to the other so that they are as a single aggregate [living together] with the gentile, their deeds are of no consequence" Mishneh Torah, Eruvin 2:10.
As Steinsaltz explains in Steinsaltz on Mishneh Torah, Eruvin 2:10:1:
"According to the law of a single individual dwelling with a gentile... the permission stems from the fact that it is uncommon for a single individual to live with a gentile... but for many who subordinated to each other and became like one, this reason does not apply."
You cannot play corporate games or use internal restructurings to wipe away the veto rights of external contract holders. If an external vendor has a lien on your IP, or a landlord has a lease covenant, you cannot "agree among yourselves" to ignore them. You must execute a formal, transactional contract to buy out or lease their rights.
The beauty of the rabbinic solution is that this commercial rental does not need to be a market-rate transaction; it can be a nominal fee:
"one may rent the gentile's domain for less than the value of a prutah" Mishneh Torah, Eruvin 2:11.
This is the exact legal equivalent of the "$1 IP Assignment Agreement" or the "nominal consideration" clauses used to secure intellectual property rights from contractors. The law requires a transactional boundary, but it allows you to set the price of that boundary at a nominal level to ensure operational continuity.
The Decision Rule
Never rely on handshake agreements or cultural alignment when dealing with external stakeholders. If a contractor writes code for your startup, do not rely on their verbal promise that "we're all in this together." You must execute a formal IP assignment agreement with nominal consideration ($1.00) to legally "rent their domain." If you do not establish this transactional boundary, their presence will legally block your ability to package and sell your technology.
┌────────────────────────────────────────┐
│ THE CORE COUSEHOLD/COURTYARD │
│ │
│ ┌───────────────────┐ │
│ │ Founder A │ │
│ │ (Participating) │ │
│ └─────────┬─────────┘ │
│ │ (Eruv) │
│ ▼ │
│ ┌───────────────────┐ │
│ │ Founder B │ │
│ │ (Participating) │ │
│ └─────────┬─────────┘ │
│ │ │
│ ▼ │
│ ┌───────────────────┐ │
│ │ Shared Courtyard │◄────────────┐ │
│ │ (Common Space) │ │ │
│ └───────────────────┘ │ │
└─────────────────────────────────────┼──┘
│
│
┌─────────────────────────────────────────────────────────┴──┐
│ THE SYSTEM HOLDOUTS │
│ │
│ ┌────────────────────────┐ ┌──────────────────────┐ │
│ │ Internal Holdout │ │ External Holdout │ │
│ │ (e.g., Unaligned Angel)│ │ (e.g., Contractor) │ │
│ └───────────┬────────────┘ └──────────┬───────────┘ │
│ │ │ │
│ │ [Bitul Reshut] │ [Sechirat] │
│ │ (Subordination) │ (Nominal │
│ ▼ │ Rental) │
│ ┌────────────────────────┐ ▼ │
│ │ Waiver of Veto / │ ┌──────────────────────┐ │
│ │ Drag-Along Signed │ │ $1 IP Assignment │ │
│ └────────────────────────┘ └──────────────────────┘ │
└────────────────────────────────────────────────────────────┘
Policy Move
To operationalize these insights and protect your company from holdout-induced paralysis, you must implement a structured Governance and IP Hygiene Protocol.
This protocol translates the rabbinic concepts of Bitul Reshut (subordination of domain) and Sechirat Reshut (rental of domain for less than a prutah) into a concrete operational framework.
The Policy: The "Nominal-Consideration & Automatic-Subordination" (NCAS) Framework
This framework consists of two core operational policies:
1. Internal Cap Table Hygiene (The Bitul Clause)
Every equity issuance—whether to co-founders, early employees, advisors, or angel investors—must be subject to a universal shareholder agreement that includes an Automatic Proxy and Drag-Along Covenant.
- The Threshold: Any shareholder holding less than 3% of the fully diluted equity of the company must automatically grant an irrevocable, standing voting proxy to the sitting Board of Directors for any matter requiring shareholder approval, provided that the transaction treats all shares of the same class equally.
- The Sincerity Covenant: To prevent the "willingly transferring the article" failure mode, any former employee or founder who retains equity but leaves the company must sign an Operational Disengagement Covenant. This covenant stipulates that if they attempt to contact current employees regarding company operations, access company systems without authorization, or publicly represent themselves as active agents of the company, their remaining unvested shares are immediately forfeited for cause, and their vested shares are automatically converted into non-voting common stock.
2. External Vendor and Contractor Onboarding (The Sechirat Clause)
You must establish a hard operational rule: No payment is processed, and no code is deployed to production, without a fully executed Proprietary Information and Inventions Agreement (PIIA) containing a nominal $1.00 consideration clause.
- The Mechanics: Even if a contractor is a close friend or a highly trusted advisor, they must sign an agreement stating: "In consideration of the sum of One Dollar ($1.00) and other good and valuable consideration, the receipt and sufficiency of which are hereby acknowledged, Contractor hereby assigns all rights, title, and interest in the Work Product to the Company..."
- This creates a clean transactional boundary, ensuring that an external party cannot later claim ownership of your intellectual property by arguing there was no "mutual consideration" for their work.
Metric / KPI Proxy: The Holdout Risk Coefficient (HRC)
To measure the effectiveness of this policy, your legal and operations teams should track the Holdout Risk Coefficient (HRC) on a quarterly basis.
$$\text{HRC} = \frac{\text{Veto-Capable Cap Table Entities} + \text{Unsigned External Contractors}}{\text{Total Enterprise Value Creators}}$$
Where:
- Veto-Capable Cap Table Entities: Any shareholder who holds veto rights, board seat rights, or whose physical signature is required to close a financing round or sale (i.e., those who have not signed the drag-along or proxy agreements).
- Unsigned External Contractors: Any external contractor, agency, or vendor who has contributed code, design, or marketing materials to the company without a fully executed PIIA containing a nominal consideration clause.
- Total Enterprise Value Creators: The total number of employees, founders, and active investors in your ecosystem.
Target Metric
Your target HRC must be 0.00.
Any score above 0.00 represents a critical vulnerability where a single "resident of the courtyard" can freeze your ability to carry your company's value to market.
Board-Level Question
"If we had to execute an emergency $10M recapitalization round or a company sale within 72 hours, how many individual signatures would we legally require to close the transaction, and what is our operational protocol for the ones we cannot reach?"
This question is designed to expose hidden governance liabilities before they disrupt a transaction. When you ask this at your next board meeting, do not accept vague assurances like "our cap table is highly aligned." Demand a precise, quantitative breakdown of your governance architecture.
Structural Vulnerabilities to Probe
- The Unresponsive Angel: Look at your early-stage convertible notes. Do you have legacy investors who have not converted to priced shares but still hold consent rights over future debt issuances or acquisitions? If so, they are the "residents who did not join the eruv." You must clean this up immediately by converting them or securing their standing proxies.
- The Ambiguous Founder Transition: Examine the separation agreements of any departed co-founders. Did they retain voting common stock? Do they still have the right to inspect your books or attend board meetings? If they do, they have the power to disrupt your company's focus. You need to transition them to non-voting structures or execute a clean buyout of their voting rights.
- The Contractor IP Trap: Ask your CTO to run a audit of your codebase against your contractor agreements. Has any critical code been written by an offshore agency or an independent contractor whose contract did not include a clear, nominal-consideration assignment clause? If so, you do not fully own your "courtyard." You must execute retroactive assignment agreements immediately.
Takeaway
Business velocity requires spatial and operational continuity. In a shared enterprise, you cannot allow the non-participation, passive resistance, or unaligned incentives of a single actor to paralyze the collective momentum of your company.
When structural coordination fails, do not allow the system to freeze. Apply the wisdom of the Sages: use formal subordination (Bitul) to align internal stakeholders, and nominal transactional contracts (Sechirat) to secure your boundaries with external ones. Keep your cap table clean, your governance streamlined, and your operational courtyard open for business. Keep carrying your payload forward.
derekhlearning.com