Mishneh Torah, Divorce 1-3

Hook

Founders often treat "formalizing a relationship" as a secondary administrative hurdle—something to be "handled" by legal counsel once the deal is already done. We live in a move-fast-and-break-things culture where an email, a Slack message, or a verbal handshake is often treated as equivalent to a binding contract. But look at your cap table, your vesting schedules, or your co-founder agreements. When the "breakup" happens—and in startups, it is a matter of when, not if—the informality you relied on becomes the source of your litigation.

The Rambam, in Mishneh Torah, Divorce 1:1, makes a radical claim: informality is a bug, not a feature. He argues that a divorce cannot happen through speech alone because speech is ephemeral, subjective, and prone to revisionist history. By mandating a get (a formal, written document) and specific, ritualized conditions for its transfer, the Torah isn't just creating a religious hurdle; it is creating a high-fidelity audit trail.

If you are a founder, your "divorce" from a vendor, a partner, or an employee needs to be as legally precise as the get. If your separation process is ambiguous, you are not just risking bad feelings—you are risking the continuity and the liability of the entire entity.

Analysis

Insight 1: The Necessity of "For Her Sake" (Intentionality)

The Rambam specifies that the document must be "written for the sake [of the woman being divorced]" (Lishmah). In business, this is the difference between a generic template and a bespoke termination agreement. When you use a "fill-in-the-blank" contract for a critical exit, you are failing the Lishmah test.

• The Rule: A legal document is only as strong as its specific intent. If you are offboarding a co-founder, a generic "release of claims" template drafted for a low-level contractor will likely fail because it lacks the specific intent required for the complex equity and IP history of a founder. You must draft for the specific relationship you are severing, not the general category.

Insight 2: The "Hand-to-Hand" Transfer (Finality)

The text insists that the divorce is not effective until the document is placed "in her hand" or her domain. The Torah rejects the idea of a "constructive" or "implied" divorce. It demands a physical act of transfer.

• The Rule: In the digital age, we rely on "deemed delivery" via email. But in high-stakes exits, you need a handshake or a physical signature that signifies the moment of severance. If you are firing a key executive, don't do it via a "notice of termination" that sits in their inbox. Ensure there is a moment of clear, unambiguous delivery—a "hand-to-hand" exchange that both parties recognize as the definitive end. Ambiguity is the enemy of closure.

Insight 3: The Role of Witnesses (The Audit Trail)

Rambam notes that witnesses are required because "it is impossible that on one day a woman will be considered to be forbidden... and on the next day she should be permitted... unless [the divorce is observed by] witnesses."

• The Rule: Your board and your legal counsel serve as your witnesses. If you are doing "quiet" layoffs or "off-the-record" equity buybacks without proper witness documentation, you are creating a "he-said, she-said" scenario that can haunt you in a Series B or C due diligence process. If the event wasn't witnessed and notarized, it essentially didn't happen in the eyes of the law. You need independent, non-interested parties to certify that the separation was executed according to policy.

Policy Move

The "Clean-Break" Protocol. Most startups allow offboarding to bleed into the following weeks (e.g., "we'll just use your email for a few more days"). This is a violation of the principle that the relationship must be "utterly severed."

Process Change: Implement a hard-switch termination policy.

1. The "Get" Document: Every separation must be accompanied by a single, definitive "Release and Severance Agreement" that specifically references the assets and IP being returned.
2. Witnessed Delivery: Termination meetings must include an HR lead or legal counsel—not just the manager. They act as the eidei kiyyum (notarizing witnesses).
3. The Hard Stop: Once the document is "placed in the hand," all access to company systems, email, and IP-generating tools is revoked immediately. KPI Proxy: "Days-to-Access-Revocation." This should be 0. If it is greater than zero, your "divorce" is not effective, and you are leaving the company vulnerable to post-divorce liability.

Board-Level Question

"If this partnership or employment relationship were to be challenged in court three years from now, does our documentation demonstrate that we were specifically focused on this individual, or did we rely on a generic template that could apply to anyone? Furthermore, have we established a 'witnessed' moment of severance that removes any doubt about the timing of the transition of control?"

Takeaway

The Torah’s rules on divorce are not about the end of a relationship; they are about the clarity of the end. A "messy" divorce ruins the company's valuation and the founder's reputation. By adopting the high-fidelity, high-intent, witnessed-based rigor of the get, you protect the entity from the "adultery" of past relationships—where former partners claim continued ownership, access, or rights to IP long after they should have left. Build your offboarding processes to withstand the scrutiny of history, not just the convenience of the moment.