Mishneh Torah, Heave Offerings 4-6

Hook

In the high-stakes world of startup scaling, the "Founder’s Dilemma" often masquerades as a question of delegation. You are drowning in the weeds, your burn rate is ticking upward, and you need to offload critical functions—product decisions, financial oversight, or partner management. The temptation is to treat every capable person in your orbit as an extension of your own intent. You authorize, you delegate, and you expect the outcome to be as if you did it yourself.

But here is the hard truth that burns through the ego of every visionary: Authority is not a commodity. Just because someone is technically "in the room" or on the payroll doesn't mean they possess the moral or functional agency to act in your stead. The text we are examining today, Mishneh Torah, Heave Offerings 4:1, confronts the founder who assumes that permission equals power. It forces a brutal distinction between an "agent" who can bind you to a commitment and a "third party" whose actions might be well-intentioned but fundamentally lack the legal and ethical standing to count.

When you scale, you are building an ecosystem of agency. If you don't understand the boundaries of that agency, you aren't building a company—you are building a house of cards. This text serves as a diagnostic tool for your organizational chart. It asks: Who actually has the authority to speak for the mission? Who is just making noise? And, most importantly, when does your silence count as consent, and when does it leave you exposed to a liability you never authorized? If you are a founder who finds yourself constantly fixing the "unauthorized" decisions of your team, you are failing to define the covenant of your company. It is time to look at the law of the agent—not as a dusty religious requirement, but as a framework for professional integrity and operational precision.

Analysis

Insight 1: The Covenant of Agency (Fairness)

The text establishes a non-negotiable rule: "A gentile may not be appointed as an agent, because... 'also you' [implies an equation between you and your agent]. Just as you are a member of the covenant, your agent must be a member of the covenant" (Mishneh Torah, Heave Offerings 4:1).

In a business context, this is the ultimate vetting protocol. Before you grant a team member the power to act on your behalf—to sign contracts, represent your brand, or commit your capital—they must share your fundamental alignment. This is not about demographics; it is about "covenant." An agent must operate from the same baseline of values and obligations as the founder. If there is a disconnect in the "why," the "what" will inevitably fail. You cannot outsource your integrity to someone who doesn't feel the weight of your company's mission. If an agent doesn't share your fundamental commitment to the company's "covenant," their actions, no matter how efficient, do not effectively represent your intent.

Insight 2: Silence vs. Consent (Truth)

The text provides a nuanced view on what constitutes permission: "When the owner comes and says: 'You should have taken better ones,' if there are better ones than those separated as terumah, the separation is effective... because [the owner] did not object" (Mishneh Torah, Heave Offerings 4:4).

This is a masterclass in feedback loops. As a founder, you are often managing by exception. You cannot oversee every micro-decision. The text suggests that if you have empowered someone and they act, your silence after the fact—when you have the opportunity to object—acts as a ratification of their agency. However, this only applies if the agent is acting toward a standard you would have set yourself. If the agent makes a decision that is objectively suboptimal, and you don't object, you own that outcome. Your lack of intervention is a policy move. This forces you to be hyper-attentive to the "first outputs" of any new process. You don't have to micromanage, but you must audit the first iteration to signal whether the agent’s judgment is aligned with yours.

Insight 3: The Burden of Professionalism (Competition)

The text notes, "When a person tells his agent: 'Go and separate terumah for me'... we do not assume that [he] actually separated... [because] 'an agent can be assumed to have carried out his mission' only when that leads to a stringency, not when it leads to a leniency" (Mishneh Torah, Heave Offerings 4:7).

This is the most "ROI-minded" insight in the text. In business, we often operate with "lazy trust"—we assume a task is done because we assigned it. The text argues that you should never assume a job is completed if that assumption creates a "leniency" (an excuse to skip a necessary step or quality check). If the task is critical to your product’s integrity or your customer’s experience, "I thought he did it" is not a defense; it is a failure of leadership. You must build internal controls that verify mission-critical tasks by default, because an agent’s failure to perform is a risk you carry, not them. Do not rely on the "good faith" of an agent when the consequences of failure are high. Verify, document, and close the loop.

Policy Move

The "Agent’s Covenant & Audit" Framework

To operationalize the principles found in Mishneh Torah, Heave Offerings 4:1-10, you must move away from informal delegation to a formalized "Agency Covenant."

The Process Change:

1. Defining the Covenant: Every person with "Delegated Authority" (the ability to make decisions that bind the company) must undergo a "Covenant Alignment" session. This is not HR fluff. It is a 30-minute review of the company’s "Non-Negotiables." If they do not explicitly agree to these, they are not agents; they are task-executors.
2. The "No-Assumption" Clause: Implement a mandatory "Confirmation of Completion" protocol for every delegated task that involves a compliance or quality risk. No agent is permitted to move to the next stage of a project until the previous stage is verified in the CRM or Project Management tool.
3. The "Objection Period": For mid-level decisions, implement a "Public Log of Authority." When an agent makes a significant decision, they log it in a shared channel. The founder has a set 48-hour window to "Object or Ratify." If you do not object, the decision is treated as yours, and you are barred from complaining about it later. This forces the founder to stay engaged without needing to be involved in the actual labor of the decision.

KPI Proxy: The "Leniency Ratio." Track how many mission-critical tasks are marked as "done" without evidence of completion or audit. Aim for a ratio of zero. If you are operating at anything higher, you are running a company on "hope," which is not a strategy.

Board-Level Question

"We are currently delegating [X major decision/function] to our team. Given that we are ultimately responsible for the outcome, what specific 'stringency' controls have we implemented to verify that these agents are not just acting, but acting in total alignment with our core covenant, and what is the specific cost to us if we are wrong?"

Takeaway

The law of the agent is a law of boundaries. As a founder, your power is not infinite; it is only as strong as the people you have properly authorized and the processes you have put in place to verify their performance. If you want to scale, stop pretending your team is an extension of your own mind. Treat them as agents within a covenant. Define the mission, authorize the action, audit the outcome, and never, ever assume that a task is done just because you delegated it. The "Mensch" founder is the one who understands that professional trust is not given; it is built through rigorous, documented, and verified alignment.