Mishnah Meilah 6:3-4

Hook

You’re a founder scaling at breakneck speed. You hire a VP of Sales or a Lead Engineer, give them a mandate, and step back. Six months later, you realize they’ve hit the revenue goals—but they did it by burning through your brand equity, misrepresenting the roadmap, or cutting corners on compliance.

The dilemma: Are you responsible for the mess they made, or is it on them for going "off-script"?

Most founders default to one of two extremes: they either micromanage every pixel and contract to avoid liability, or they wash their hands of the outcome, claiming, "I told them what to do; if they screwed it up, that’s on them." Mishnah Meilah 6:3-4 shreds both these excuses. It argues that agency isn't just about output—it's about the sanctity of the instruction. If the instruction is followed, the founder owns the result (even if they regret it). If the instruction is defied, the agent owns the liability.

This text is the ultimate audit of your delegation framework. It challenges the "Move Fast and Break Things" mantra by asking: When you empower someone, are you empowering them to act on your behalf, or are you just offloading your own moral responsibility? If you can’t answer the "agency question" with precision, you aren't leading—you’re just gambling with your company's integrity.

Text Snapshot

"With regard to an agent who performed his agency properly... the homeowner is liable for misuse... But if he did not perform his agency properly, the agent is liable... If the homeowner said to the agent: Give meat to the guests, and he gave them liver; or if he said: Give them liver, and he gave them meat, the agent is liable."

"If the homeowner said to the agent: Bring me this item or this money from the window... and the agent obeyed and brought it to him from the place that he instructed him, even though the homeowner said: In my heart, my desire was only that he should bring me the item from that other place... the homeowner is liable."

"If the homeowner gave the agent two consecrated perutot... and he went and brought him an etrog with one peruta and a pomegranate with one peruta, both of them are liable for misuse."

Analysis

Insight 1: Intent is Irrelevant, Instructions are Absolute

The Mishnah is brutal: if you give an order, you are legally tethered to the outcome, even if your internal intent was different. The text states: "Even though the homeowner said: In my heart, my desire was only that he should bring me the item from that other place... nevertheless the homeowner is liable."

In business, "but that’s not what I meant" is a failure of leadership, not an excuse for exemption. If your documentation, OKRs, or verbal briefs are ambiguous, you are liable for the "misuse" of your resources. You cannot claim the benefits of an agent's success while disclaiming the collateral damage caused by your own poor communication.

• Decision Rule: If you didn't define the "from the window or the chest" constraint, you own the outcome. Clear communication is a fiduciary duty.

Insight 2: The "Deviation Threshold"

The text introduces a nuance of scale: "The agent is liable for the second piece, which he added to the instructions of the homeowner. Finally, the guests are liable for the third piece." This is the concept of incremental liability. When an agent deviates, they don't just "break" the contract; they create a new, unauthorized one.

In a startup, this is "scope creep." If your sales lead promises a feature that doesn't exist, they have stepped outside their agency. The Mishnah suggests that once the agent deviates, the agency dissolves. They are no longer your agent; they are an independent actor.

• Decision Rule: If the action taken deviates from the defined scope, the liability shifts entirely to the agent. This is why strict, narrow agency—defined by clear boundaries—is the only way to protect the "homeowner" (the founder).

Insight 3: The "Split Liability" Trap

When instructions are partially followed and partially ignored, both the principal and the agent can be liable. As the text notes: "The homeowner is liable because his agency was performed with the purchase of the robe... and the agent is liable because he deviated from his instructions by purchasing the cloak."

This is the nightmare scenario for a cap table or a compliance audit. If you give an agent a broad budget and they use half for the intended product and half for an unauthorized add-on, you are "tainted" by the part they got right, and they are "tainted" by the part they got wrong.

• Decision Rule: Avoid "mixed-purpose" delegations. If you want to avoid liability, keep instructions discrete. If you bundle goals, you are effectively consenting to the risk of the agent's interpretation.

Policy Move: The "Scope-of-Agency" Memo

To mitigate this, implement a "Delegation Manifest" process for any transaction or strategic pivot above a defined financial threshold.

Stop using vague, high-level directives. Every major delegation must be documented with three fields:

1. The "Window" (Mandated Path): The specific authorized method/source.
2. The "Chest" (Forbidden Path): A explicit list of what cannot be done, even if it seems efficient.
3. The "Severability Clause": Acknowledgment that any deviation from the "Window" renders the action unauthorized and the agent personally responsible for the variance.

Metric/KPI Proxy: Deviation Rate. Track how often "Authorized Spend/Action" matches "Actual Outcome." A high deviation rate isn't just a process failure; it is a signal that your agency structure is leaky and your liability exposure is growing.

Board-Level Question

"If we look at our last three major strategic pivots or procurement cycles, can we point to a specific document where the 'bounds of agency' were defined, or were we operating on 'implied intent'? If we were to be audited on the consequences of those decisions, which parts of the outcome would the company (the homeowner) be forced to own, and which parts would we be able to legally and ethically pin on the individual agents who executed them?"

Takeaway

You are the architect of your own liability. If you want the autonomy of your team to be a force multiplier rather than a liability, you must stop being vague. The Mishnah teaches that the "homeowner" is only safe when the instructions are precise. Precision is not micromanagement—it is the highest form of respect for your team and the only way to protect your firm's integrity. Lead with the clarity of a judge, not the ambiguity of a dreamer.