Mishneh Torah, Levirate Marriage and Release 6-8

Hook

Founders are obsessed with "product-market fit," but they often ignore "founder-entity fit." You wake up one day and realize your co-founder isn't just underperforming—they are an existential risk to the cap table or the brand’s integrity. You’re in a "levirate" situation: you’re shackled to a legacy, a contract, or a partnership structure that was designed for a different season, and now you’re trying to figure out if you have to "marry" (commit to) the liability or "release" (terminate) it.

The real dilemma isn't whether you want to be there. It’s whether you can leave without nuking the company’s future. In Mishneh Torah, Levirate Marriage and Release, Rambam outlines a complex matrix of who is fit to "build the house" and who must be released. The text is brutal in its clarity: if the partner is inherently unfit (a "saris" or "mentally incompetent"), there is no obligation. You don't perform surgery on a dead limb. But if the partner is "fit" but technically forbidden, the rules of engagement change. The founder’s trap is assuming that because you are in a relationship, you are obligated to sustain it. Rambam suggests that "building the name of the deceased" (the mission) is the only KPI that matters. If the partner or the structure prevents the mission, the obligation dissolves. Are you holding onto a co-founder because they are the "firstborn" of the idea, or are you just afraid of the legal "chalitzah" (the messy, public release process)? Most founders are terrified of the "chalitzah"—the PR fallout, the messy buyout, the public acknowledgment of the split. But as this text argues, staying in an incompatible union isn't "loyalty"—it's a violation of the mission’s survival.

Text Snapshot

"There are brothers who are fit to perform the rite of yibbum... and there are brothers who are not fit... The deceased's wives are under no obligation to them at all; they may marry another man." (Halachah 6)

"[The rationale is that] the entire purpose of yibbum is to perpetuate the deceased brother's name... when this is not possible there is no obligation for this rite." (Halachah 7)

"If [a yavam] who has been castrated enters into relations [with his yevamah], he acquires [her as a wife]... He must, however, divorce her with a get, because he is forbidden to marry [a native-born Jewess]." (Halachah 9)

Analysis

Insight 1: The Principle of Functional Competence

Rambam’s taxonomy of "fit" and "unfit" brothers serves as a harsh lesson in operational reality. He distinguishes between those who are physically or mentally capable of carrying the burden of the mission and those who are not. If a co-founder or an early-stage investor is "mentally incompetent" or "impotent" regarding the current strategy, the "obligation" to them is void.

Decision Rule: Do not confuse historical proximity with current utility. In business, "legacy" is not a substitute for "competence." If your partner cannot contribute to the "perpetuation of the name" (the company’s growth), they are effectively a "saris chamah"—a partner who never possessed the capacity to drive the mission forward. You have no moral or contractual obligation to "marry" the liability.

Insight 2: The Priority of the Mission Over the Taboo

Halachah 10 touches on the most uncomfortable intersection: the case where a yavam is forbidden to the yevamah by a negative commandment, yet the positive commandment of yibbum (the mission) creates a binding bond if he acts. This is the "move fast and break things" of the Torah. Sometimes, the urgency of the mission mandates an action that would otherwise be "taboo" (like a messy pivot or a difficult firing).

Decision Rule: Where a positive mandate (the success of the company) conflicts with a secondary restriction (a fragile office culture or a fear of awkwardness), the mandate to preserve the "house" takes precedence. If you need to fire a legacy hire to save the company, do it. The "taboo" of the firing is less significant than the "mitzvah" of the company’s survival.

Insight 3: The "Superior" vs. "Inferior" Release

Rambam emphasizes that some releases are "superior" (binding and clean) while others are "inferior" (incomplete). A "superior" release clears the board for everyone. A founder who performs a half-baked exit (an "inferior" release) leaves the company in a state of perpetual limbo where other stakeholders are still "chained" to the dead-weight partner.

Decision Rule: Never execute a "soft" exit. If you are parting ways with a partner, the release must be absolute. A half-measure—like keeping them on as an "advisor" when they are actually an "ervah" (a prohibited presence)—will only trigger a chain reaction of legal and operational restrictions that will eventually sink the "house."

Policy Move

Implement the "Mission-Cap" Review Process.

Every quarter, the board must conduct a "Levirate Audit." This is not a performance review; it is a structural audit.

1. The Capacity Check: Does this partner/leader have the capacity to "father" the next phase of the company? If they are a "saris" (incapable of the growth required), they are not obligated to the company, and the company is not obligated to them.
2. The "House" KPI: We will track the "Mission-to-Liability Ratio." If a partner’s presence creates more "negative commandments" (legal risk, cultural toxicity, slow decision-making) than "positive mandates" (product output, revenue, leadership), the relationship is officially flagged for chalitzah.
3. The "Clean Break" Policy: No "advisor" titles for ousted founders. No "consultant" contracts to save face. If the relationship is incompatible, we execute a full get (divorce) and chalitzah (public release). This ensures that the cap table is clean and the remaining "brothers" (the leadership team) are free to build the house without the baggage of a previous, failed bond.

KPI Proxy: "Percentage of equity held by non-active, legacy stakeholders." If this number exceeds 5%, you have a "Levirate" crisis in your cap table.

Board-Level Question

"If we had to build this company from scratch today, would we invite every current stakeholder to the table? If the answer is 'no,' why are we treating our current obligation to them as more important than our obligation to the survival of the 'house' we are building?"

Takeaway

Loyalty is not the same as enabling. Rambam teaches us that the law provides complex mechanisms to dissolve relationships that hinder the mission. Your job as a founder is not to preserve the status quo of your partnerships, but to ensure that the "house" remains standing. If a partner is an "ervah"—a prohibited, destructive element—even if they were once a "brother," you must have the courage to perform the chalitzah and walk away. The mission is the only name that matters. Don’t let a dead-end relationship erase your future.