Mishneh Torah, Divorce 7-9

Hook

In the high-stakes world of startup operations, we often obsess over the "what"—the product, the pitch, the term sheet. But the most catastrophic failures in business aren't usually product-market fit issues; they are failures of provenance. How do you know the data you’re relying on is authentic? How do you ensure that a key decision, made by an agent or a middle manager, is as binding as if you had signed it yourself?

Founders often fall into the trap of believing that "trust" is a substitute for process. You hire a VP, you send them to lead a series-B negotiation, or you delegate a critical partnership to a regional manager. What happens when that person goes rogue, or, more likely, when the counterparty challenges the legitimacy of the agreement months later? "I never authorized that," or "That document is a forgery," are the phrases that kill companies.

The text from Mishneh Torah, Divorce 7-9 deals with the mechanics of the get (divorce document) as it moves through space and time via agents. It sounds like an archaic family law text, but it is actually a manual on distributed trust systems. It addresses the "Founder’s Dilemma of Delegation": How do you maintain the integrity of a mission-critical document when it is being handled by an intermediary who wasn't there at the inception?

Rambam teaches us that the burden of proof is not just a legal technicality; it is a structural necessity for business continuity. If you haven't built a protocol for verifying the "signature" of your agents, you are operating in a state of permanent risk. Your business is not "divorced" from its liabilities until the verification process is airtight. If you fail to design for the verification of your own delegated authority, you are leaving your company’s future to the whims of a protest—and as Rambam notes, when there is no proof, the entire arrangement collapses, leaving you with "illegitimate" outcomes.

Analysis

Insight 1: The Protocol of "Presence" as a Verification Metric

Rambam emphasizes, "Although [the agent] did not witness the writing of the get... [the agent] may give [the woman the get] in the presence of witnesses" (7:1). The core insight here is that trust is not a binary state; it is a procedural requirement.

In business, we often accept a document or a deal from a subordinate without verifying its "writing." We assume that because the person is ours, the document is authentic. Rambam rejects this. He requires the agent to serve as a bridge of truth. If the agent cannot attest that the document was "written and signed in my presence" (7:5), the transaction is fragile.

Decision Rule: Never delegate a mission-critical signature or contract without a "Verification Protocol." If your agent cannot explain the origin of a document or the specific intent of the parties at the moment of creation, that document is a liability waiting to be contested. You must require your agents to be witnesses to the process, not just carriers of the output.

Insight 2: The "Hate" Risk (Conflict of Interest)

Rambam is ruthlessly pragmatic regarding human nature: "Women who we presume hate each other are not trusted to bring a get... [We suspect] it might be a forgery, because one desires that the other remarry and be forbidden to her husband" (7:1).

He identifies that agents have agendas. In startup terms, if you send an agent to negotiate with a competitor or a vendor, and that agent has a personal incentive (a future job, a vendetta, a hidden conflict), they will manipulate the "document" to serve their own interests. Rambam doesn't ask us to be naive; he asks us to map the incentives of our intermediaries.

Decision Rule: Always conduct a Conflict-of-Interest audit on any agent empowered to close a deal. If an agent has a "presumed hate" or a structural misalignment with the counterparty or the company, their agency must be revoked or strictly limited by a secondary, neutral witness. If the incentive structure is broken, the signature is void.

Insight 3: The Supremacy of Documentation over Oral Protest

Rambam notes that once signatures are verified or the agent’s testimony is accepted, "the husband's protests are ignored. Once the witnesses sign the get, it is considered as if they have testified in court" (7:1).

This is the ultimate ROI for a founder: The document creates a firewall. When you have a properly executed, witnessed, and verified protocol, you are immune to the "I didn't mean that" or "This is a forgery" protests that plague failing companies. The protest only works when the process was sloppy.

Decision Rule: Documentation is not for the "good times"; it is the weapon used to silence the "protest" in the bad times. If you haven't made it "as if they have testified in court," you have no protection. Every contract, every board decision, and every delegated authority must be documented with a level of rigor that makes future "protests" legally and operationally irrelevant.

Policy Move

Implement the "Immutable Provenance Policy" for all external-facing agreements.

Currently, most startups have a "sign and send" culture. This is a recipe for the get that becomes "unacceptable" (7:1). Under the new policy, no document leaving the company via an agent or middle manager can be considered binding unless it satisfies the "Double-Witness Protocol":

1. The Witness to Content: Every document must have a secondary employee (the "Internal Witness") who verifies the document was written for the specific purpose ("lishmah") and in the specific context of the current negotiation.
2. The Verification Statement: The agent must append a signed statement: "I testify that this document was written and signed in my presence, for the express purpose of [Company Name], and I confirm no conditions or secret stipulations were added."
3. The Audit Log: If the agent is prevented from completing their task due to "forces beyond control" (7:4), they are strictly forbidden from appointing a successor without a formal, recorded "Court Appointment" (Board or Legal Counsel approval).

Metric for Success: The "Contestation Rate." Track the number of contracts or deals that are challenged by counterparties claiming "misunderstanding" or "forgery." A successful deployment of this policy should reduce the Contestation Rate to zero, as the procedural rigor makes such claims laughably impossible to sustain.

Board-Level Question

"If our lead negotiator or primary agent were to face a protest tomorrow claiming that our documents were forged or unauthorized, what specific piece of evidence—other than their word—could we immediately present to a court to render their protest 'of no consequence' (7:1)?"

This question forces leadership to move away from relying on "trusting our people" and toward "verifying our process." If the answer is "we trust them," you are effectively running an unverified, high-risk, and ultimately illegitimate business. You are one bad day away from a total loss of the "marriage" (the partnership/contract) and a massive, unmanageable liability.

Takeaway

The Torah doesn't care about your "company culture" or your "vision." It cares about truth in transmission. If you delegate the movement of your assets, your contracts, or your reputation, you are responsible for the entire chain of custody. Rambam’s rules for the get are a masterclass in risk management: verify the signatures, monitor the incentives, and ensure that the process is so robust that even the most desperate protest from an adversary becomes a footnote in history. Be a Mensch—build processes that are as honest as they are ironclad.