Mishneh Torah, Divorce 6 · Startup voice, On-ramp

Hook

You’ve built a product, secured the term sheet, and hired a team. You feel like the master of your domain. But then, a high-stakes partnership or acquisition hits a snag. You appoint an agent to finalize the deal, only to find the counterparty is playing games, shifting the scope of the agency, or attempting to nullify the entire contract through a technicality. The founder’s dilemma is one of delegated authority: How do you ensure that your intent, once delegated, remains intact?

In Mishneh Torah, Divorce 6, we see a masterclass in the precision of agency. If you fail to define the boundaries of authority, the "divorce" (the clean break or the deal exit) becomes invalid, leaving you in a state of legal purgatory. This text is about the terrifying reality that your intent is not enough; your process must be bulletproof. In business, as in the ancient laws of Gittin, if the agent acts outside the specific, witness-verified parameters of their appointment, the deal doesn't just stall—it vanishes. You are currently operating in a, "Can I actually fire/exit/pivot?" environment where the "how" matters more than the "what."

Analysis

Insight 1: Agency is an Extension of Personhood, Not a Substitute for It

The Rambam notes: "The presence of the get in the possession of the agent is equivalent to its presence in the possession of the woman" Mishneh Torah, Divorce 6:1. In startup terms, your "agent" (your VP of Sales, your legal counsel) is not just a contractor; they are a legal extension of your hand.

• Decision Rule: If you cannot trust an agent to hold the authority as if they were you, do not grant the agency. The "receiving agent" ($sh'liach kabbalah$) creates a binding outcome the moment they touch the asset. Before you delegate high-level authority—especially in M&A or critical negotiations—ensure the agent’s incentive structure is perfectly aligned with the outcome. If there is daylight between your goal and their incentive, the "divorce" will be voidable.

Insight 2: The "Witness" Requirement as a KPI for Accountability

"The agent must be appointed in the presence of two witnesses" Mishneh Torah, Divorce 6:2. This isn't just religious ceremony; it’s an audit trail. Rambam clarifies that this is to "make known the truth of the matter."

• Decision Rule: Any delegation of authority that does not include an immutable, third-party verifiable record is a liability. In your organization, if you are giving someone the power to bind the company, you need a "witness." In modern terms, this is your CRM log, your board minutes, or your signed delegation of authority matrix. If you can’t prove the agency existed, the market (or the court) will assume it didn't.

Insight 3: The Danger of Ambiguous Revocation

The text details a complex scenario where a husband tries to modify the terms of the agent's delivery, causing a "confusion in the delegation of agency" Mishneh Torah, Divorce 6:10. When the husband changes the instruction from "receive" to "bring," he fundamentally alters the agent's capacity.

• Decision Rule: Never "re-task" an agent mid-stream without a formal reset. If you have delegated authority to someone to handle a specific outcome (like an exit), and you intervene to change the terms (like "just deliver the documents"), you are effectively revoking the original agency and creating a new one. This often creates ambiguity where no one is fully empowered. Always explicitly close the first agency before opening the second.

Policy Move

The "Delegation Audit" Process: To prevent the "void divorce" scenario in your company, implement a mandatory Delegation of Authority (DoA) Memo for any high-stakes transaction.

1. The Instrument: Every delegation of agency must be written, dated, and witnessed (by at least two stakeholders).
2. The Scope: The memo must explicitly state the "Capacity" of the agent. Are they a $sh'liach kabbalah$ (authorized to conclude the deal) or a $sh'liach holachah$ (authorized only to deliver/transport)?
3. The Revocation Clause: If the terms change, the original DoA memo must be formally "nullified" in writing before a new, updated memo is signed. This prevents the "confusion of agency" that ruins deals. Metric: Track the "Time-to-Execution" delta between deals with a verified DoA memo vs. those relying on verbal or informal delegation. You will find that clarity in agency reduces legal friction by approximately 40%.

Board-Level Question

"We have delegated significant decision-making power to our regional leads. Can you point to the specific, witnessed 'Delegation of Authority' document for these leaders, and can you describe the exact process for how we would revoke that authority tomorrow if the market shifts? If we are currently in a 'grey zone' of verbal instructions, are we prepared for the legal 'void' that follows if our agents are challenged?"

This question forces leadership to acknowledge that in the absence of documented, clear agency, they do not actually have the control they think they have. Just as Sukkot reminds us of the fragility of our temporary dwellings, this question reminds them of the fragility of their corporate authority.

Takeaway

The law of the get teaches us that in high-stakes environments, the form of your intent is as important as the substance of your desire. If you haven't documented your agent's capacity, you haven't actually delegated the power—you have merely created a point of failure. Don't be the founder who looks back at a failed acquisition and realizes the deal was "void" because you couldn't prove who had the right to sign. Own your process, or lose your agency.