Mishnah Meilah 6:3-4

Hook

You’ve delegated a mission-critical task. Your lead executes, but they take a "creative liberty" with the process. Does the liability sit with you for the outcome, or them for the deviation? In high-stakes environments, the difference between "authorized action" and "rogue operation" is the difference between a pivot and a lawsuit.

Text Snapshot

"If the homeowner said to the agent: 'Give meat to the guests, and he gave them liver... the agent is liable for misuse... as he deviated from his agency. But if he performed his agency properly, the homeowner is liable." (Mishnah Meilah 6:3-4)

Analysis

1. The Threshold of Deviation

The Mishnah establishes that agency is a contract of strict adherence. If you order "meat" and the agent delivers "liver," the agency contract is voided. Decision Rule: If your team ignores the "what" of your instruction, they own the liability of the result. If they follow the "what" but fail the "how" (e.g., procurement source), they are still liable for the deviation.

2. Clarity as Liability Shield

The text highlights cases where even if the intent was different, the instruction holds the power. If you say "get it from the window," and they do, you are liable—even if you meant the chest. Decision Rule: Never blame the agent for poor performance if your instructions were ambiguous. You are the architect of the liability; own the result of your own imprecision.

3. The "Small Deviation" Trap

A tiny deviation (e.g., swapping wicks for lamps in the wrong location) can trigger liability if the total value hits a peruta (a minimal unit of value). Decision Rule: In operations, "minor" deviations aggregate. Do not tolerate "small" process drift; it inevitably creates legal or ethical exposure.

Policy Move

Implement a "Protocol Variance Log." For any task where the agent cannot follow the exact instructions (e.g., supply chain shortages), they must seek a "Variance Approval" before action. If they deviate without this log entry, they forfeit indemnity.

Board-Level Question

"Are our current delegation workflows defined by outcomes, or by explicit process constraints? If we are being held liable for 'liver' when we ordered 'meat,' where is the breakdown in our internal authorization chain?"

Takeaway

Alignment isn't about shared vision; it's about shared execution. If your team deviates from the instructions, they have effectively left the company—and the liability stays with them. KPI Proxy: % of tasks completed with >95% adherence to Standard Operating Procedures (SOPs).