Mishnah Meilah 6:5-6

Hook

Founders are obsessed with delegation until the moment things go wrong. You hire, you set the OKRs, you provide the budget, and then you step back—only to find that your "agent" (your VP of Sales, your lead engineer, your fractional CFO) has deviated from the mission. In the heat of the sprint, they cut a corner, over-promised to a client, or reallocated resources without your sign-off. When the regulators or the board show up, the "I didn't know" defense fails. You are the homeowner, and your agents are your extension.

The Mishnah in Meilah forces a brutal confrontation with this reality. It doesn’t let you hide behind the complexity of organizational structure. It asks: Did they follow the brief, or did they freelance? If they followed your instructions, the liability is yours; if they deviated, they are on their own. But the text goes deeper. It forces us to define what "agency" actually looks like in a high-stakes environment. Does "giving them meat" mean they have the authority to decide the portion size? Does "getting money from the chest" imply that the exact location matters, or just the value of the asset?

For the modern founder, this is the architecture of accountability. We love to talk about "empowerment" and "autonomy," but the Torah reminds us that empowerment without strict boundaries isn't leadership—it’s negligence. You are legally and ethically tethered to your team's actions. If you haven't defined the "bound" vs. "unbound" nature of the assets you entrust to them, you are effectively gambling with your company’s integrity. The following analysis isn't just about ancient laws of temple property; it is a masterclass in risk management, agency, and the cold reality of fiduciary duty. If you want to scale without losing your soul—or your business—you need to understand when you own the mistake and when your employee has officially gone rogue. Let’s look at the mechanics of the agency.

Text Snapshot

• “If he did not perform his agency properly, the agent is liable... as once the agent deviates from his agency, he ceases to be an agent.”
• “If the homeowner said to the agent: Give them meat, a piece for this guest... and the agent says: Each of you take two pieces... all of them are liable.”
• “If the homeowner said: Bring me this item or this money from the window... and the agent obeyed... 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 money is bound, the money changer may not use it... if it was unbound he may use it.”

Analysis

Insight 1: The Principle of Strict Adherence (Agency is Binary)

The text posits a binary: “If he did not perform his agency properly, the agent is liable... as once the agent deviates from his agency, he ceases to be an agent.”

In startup culture, we often reward "initiative." We tell our teams to "figure it out." But the Mishnah provides a sharp correction: when managing high-stakes assets (whether intellectual property, capital, or brand reputation), initiative that contradicts the mandate is not innovation—it is a breach of contract. Once an agent deviates from the specific instructions, they lose the protection of the principal-agent relationship.

Decision Rule: If your instructions are ambiguous, the agent is effectively flying blind. You must distinguish between "Outcome-based mandates" (get me the money) and "Process-based mandates" (get it from the chest). When the agent deviates from the process you defined, they are no longer acting for you; they are acting for themselves. Your job as a founder is to define the "process" for high-risk domains and the "outcome" for low-risk ones. If you try to enforce process on low-risk items, you become a micromanager. If you provide only outcomes on high-risk items, you are a negligent founder.

Insight 2: The Multi-Layered Liability of Scaling

The case of the guests taking extra meat—“the homeowner is liable for the first piece... the agent is liable for the second... the guests are liable for the third”—is a brilliant taxonomy of operational failure.

1. The Homeowner (Founder/CEO): Liable for what they explicitly authorized. If you tell your sales team, "Do whatever it takes to close the deal," you are liable for the first layer of unethical behavior or over-promising, because you authorized the general mandate.
2. The Agent (Manager/Lead): Liable for the deviation. When the manager stretches the rules—"I know the CEO said X, but we can squeeze in Y"—the manager enters the zone of personal liability.
3. The Guest (End User/External Party): Liable for their own opportunistic behavior.

Decision Rule: You are the "Homeowner." You must document the "first piece" of every transaction. If you haven't explicitly set the boundaries, you are on the hook for the entire "second piece" of the agent's overreach. You cannot complain about "rogue employees" if your initial mandate was effectively "anything goes."

Insight 3: The "Bound" vs. "Unbound" Asset Framework

The distinction between “bound” and “unbound” money is the most critical insight for a founder’s treasury management. If money is "bound" (earmarked for a specific, restricted purpose), the agent has no right to use it for operations. If it is "unbound" (general capital), they have implicit authority to circulate it.

Decision Rule: Everything in your company should be classified as either "Bound" or "Unbound."

• Bound: Capital for payroll, legal reserves, or specific R&D grants. If an agent touches this, they are in violation of the "binding."
• Unbound: Operational expenses, marketing spend, T&E.
• Metric: "Asset Velocity vs. Restriction Ratio." Keep a dashboard of what funds are "bound" by contract or board policy. If an agent treats a "bound" asset as "unbound," you have a systemic culture issue that requires immediate termination or restructuring, not just a slap on the wrist.

Policy Move

The "Mandate Documentation" Protocol:

To prevent the "I thought you meant..." syndrome, every significant delegation of authority ($5k+ spend or high-risk client commitment) must be accompanied by a "Mandate Snapshot."

1. The Directive: What is the core task?
2. The Constraints (The "Chest vs. Window"): What are the non-negotiables? (e.g., "You can choose the vendor, but the cost must be under $10k and they must sign our standard MSA").
3. The "Bound" Declaration: Clearly state if the resources used are restricted or unrestricted.

Process Change: If a manager exceeds the "Mandate Snapshot," the company’s internal audit process (or a designated "Ethics Lead") must trigger an automatic review. If the deviation was a "good faith, high-reward" move, the policy is updated to include it. If it was a "bad faith or negligent" move, it is logged as a personal liability of the agent. This removes the ambiguity of "I was just doing my job" and places the burden of clarity on the person issuing the command (you) and the burden of compliance on the person executing it (them).

Board-Level Question

"When we look at our current operational risk, where are we treating 'Bound' assets as if they were 'Unbound,' and have we clearly articulated the difference to our VPs? Are we, as a Board, comfortable with the level of 'Agent Liability' our current reporting structure creates, or are we inadvertently shielding ourselves from the responsibility of our own unclear instructions?"

Strategic focus: This forces the board to stop looking at high-level KPIs and start looking at the integrity of the delegation chain. It exposes whether you have a culture of rogue agents or a culture of poorly defined mandates.

Takeaway

The Mishnah teaches us that you cannot separate the principal from the agent. If you are the founder, you are the homeowner. If you want to scale, you must be precise with your mandates, rigorous about your asset restrictions ("bound" vs. "unbound"), and honest about whether the failure was a rogue agent or your own lack of clarity. Stop empowering people to make decisions you aren't prepared to be held liable for.