Mishneh Torah, Divorce 4-6

Hook

The founder’s dilemma is rarely about the intent of a contract; it is about the permanence and legibility of the commitment. You’ve been there: you shake hands on a partnership, you draft a term sheet, or you send a critical email confirming equity stakes. Everything feels solid. But six months later, when the market shifts or a co-founder leaves, you discover that your "ink" was actually written in fruit juice. It hasn't left a permanent impression.

In the language of Maimonides, you have a get—a bill of divorce—that is legally void because it lacked the substance to endure. Founders often operate in the realm of "beverages and fruit juices"—fluid, fast, and ephemeral agreements that depend on current good feelings rather than structural clarity. When the heat of a crisis hits, these soft commitments evaporate.

This text forces us to confront a brutal truth: If your core business agreements, equity splits, or exit strategies cannot be read by a "child of average intelligence" and aren't written in a substance that resists erasures, you aren't building a company; you are building a liability. The Rambam isn't just discussing divorce law; he is discussing the mechanics of binding reality. In business, as in Torah, a document that allows for "two meanings" is not a contract; it is a future lawsuit. The dilemma for every founder is whether you are writing with permanent ink that survives the friction of time, or sketching with charcoal that smears the moment you start building. Are your agreements designed to hold, or are they designed to be easily "rubbed out" when the relationship turns cold?

Text Snapshot

"A get may be written only with a substance that leaves a permanent impression... If, however, [a get] is written with a substance that does not leave a permanent impression - e.g., beverages, fruit juices or the like - the get is void."

"The scribe must be careful that the wording of the get does not allow for two meanings... the wording should unequivocally state one concept."

"The writing should not be crooked, nor incoherent, lest one letter be confused with another, changing the meaning of the text."

Analysis

Insight 1: Substance Over Speed (The Permanence Rule)

The Rambam insists that a get requires a substance that leaves a "permanent impression." In the startup world, we prioritize speed. We use Slack, WhatsApp, and verbal "syncs" to finalize decisions that impact equity and IP. These are the "fruit juices" of business law.

The decision rule here is simple: If you cannot audit it in three years, it doesn't exist. When you are closing an investment round or setting vesting schedules, stop asking if the parties agree today. Ask if the document is written in a medium that survives the departure of the current team. If your "contracts" are stored in ephemeral threads or depend on the memory of people who will eventually leave, you are operating in a state of constant legal voidance.

Insight 2: Elimination of Ambiguity (The Truth Rule)

Maimonides warns that a document allowing for two meanings is unacceptable because it creates doubt: "Perhaps this was his intention... or perhaps this was his intention." In business, ambiguity is not a feature; it is a bug that eventually kills the company.

The decision rule: If a clause can be interpreted in two ways, the "good faith" of the parties will not save you. You must draft for the adversarial scenario. If a phrase can be read as a "joke" or as a "binding commitment," it is effectively void. High-performing founders strip away the "and/or" language that plagues early-stage contracts. You must ensure that your documents are so clear that a neutral third party—the "child of average intelligence"—can read them and reach only one conclusion. If it requires a 45-minute explanation of the "founder's spirit" to understand a vesting clause, you have failed the test of the get.

Insight 3: The Clarity of the Medium (The Competition Rule)

The text notes that even if a get is written in a foreign language, it is valid provided the witnesses comprehend it. However, it mandates that the writing must be clear and distinct.

The decision rule: Your operational stack is your evidence. In competition, your ability to prove your ownership, your IP rights, and your corporate governance is your defense. If your internal documentation—your cap table, your board minutes, your IP assignments—is "crooked or incoherent," you are inviting competitors to challenge your legitimacy. When the "divorce" comes (a founder exit, an acquisition, a pivot), the only thing that matters is the record. If your records are sloppy, you are essentially leaving your company’s future to the mercy of a court’s interpretation rather than the strength of your own clear, documented intent.

Policy Move

The "Get-Standard" Documentation Audit.

Every quarter, your COO or legal counsel must conduct a "Get-Audit." This is not a standard legal review; it is a stress test for permanence.

1. The Permanence Test: Identify every critical agreement made in the last 90 days. If an agreement exists only in email, chat, or verbal form, it must be migrated into a formal, signed document with a permanent timestamp.
2. The "Average Intelligence" Test: Take a junior intern—someone who was not involved in the original negotiation—and ask them to read your primary agreements. If they cannot explain the core commitments (vesting, IP ownership, decision-making authority) back to you in plain language, the document is "void" and must be redrafted for clarity.
3. The Erasure Check: Ensure all critical documents are stored in a centralized, immutable ledger (e.g., a secure, version-controlled document repository with audit trails). If a document can be modified or deleted without a clear record of the change (the "erasure" mentioned by the Rambam), it is a liability.

Metric: Document Velocity to Finality. Measure the time between a verbal agreement and the execution of a "permanent" document. If your velocity is >14 days, your "fruit juice" is drying up.

Board-Level Question

"If we were to face a hostile takeover or a sudden, contentious exit by one of our key founders tomorrow, which of our current governance documents would a court immediately throw out for being 'ambiguous' or 'lacking permanent impression'?"

This question forces leadership to move away from the comfort of "we’re all friends here" and into the reality of "we are a legal entity." It shifts the focus from the relationship (which changes) to the commitment (which must be absolute). It exposes the "fruit juice" agreements that everyone pretends are ironclad but that would disintegrate under the scrutiny of a legal audit.

Takeaway

A company is essentially a collection of promises. If those promises are written in ink that fades or in language that obfuscates, you are not building a sustainable entity; you are living on borrowed time. The Rambam teaches that the form of the commitment is as vital as the intent of the commitment. Stop managing for the best-case scenario of ongoing harmony, and start managing for the worst-case scenario of total dissolution. If your contracts aren't permanent, clear, and unambiguous, you aren't ready to lead.