Daily Mishnah · Startup Mensch · Bite-Sized

Mishnah Meilah 6:5-6

Bite-SizedStartup MenschMarch 26, 2026

Hook

You’ve delegated a critical project to a lead, but they delivered a slightly different output than you envisioned. Are you liable for the fallout, or are they? In the high-stakes world of startups, "execution drift" isn't just a management nuisance—it’s a legal and ethical liability.

Text Snapshot

“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... as he deviated from his agency.” (Mishnah Meilah 6:5)

Analysis

1. Deviance Voids Agency

The text is binary: if your agent follows instructions, the liability rests with you (the principal). If they deviate, the agency bond breaks, and they own the consequences. Decision Rule: If your team ignores the "spec" (meat vs. liver), they aren't just making a creative choice; they are acting on their own account. You aren't responsible for their unauthorized pivots.

2. The "Bound vs. Unbound" Expectation

The Mishnah distinguishes between "bound" money (held in trust) and "unbound" money (intended for circulation/use). Decision Rule: Clarity on intent is your primary defensive wall. If you give a team member a budget without explicit "bound" constraints (e.g., specific budget buckets), you are implicitly authorizing them to circulate/spend as they see fit.

3. The Liability of the "Third Piece"

The text notes that if an agent adds a piece of meat beyond your instructions, they are liable for that specific excess. Decision Rule: Distinguish between incremental improvement and unauthorized expansion. When a lead over-delivers, they’ve moved from "agent" to "principal" of that extra effort.

Policy Move

Implement a "Scope-Lock" Protocol: For every major delegation, document the "Liver vs. Meat" threshold. Explicitly define what constitutes a "minor pivot" (within agent discretion) versus a "material deviation" (requires re-authorization).

  • KPI Proxy: "Deviation Rate" (Number of tasks redirected back to the founder due to scope misalignment).

Board-Level Question

"When our teams deviate from the original product roadmap to pursue an 'opportunity,' are we treating that as a failure of agency or an evolution of strategy—and who is currently carrying the risk for that deviation?"

Takeaway

Don't be a passive principal. If you don't define the boundaries of your agents' authority, you own every "liver" they decide to serve instead of the "meat" you ordered.