Daf Yomi · Startup Mensch · Standard
Chullin 85
Hook
Every founder has a graveyard of "phantom work."
You know exactly what this looks like:
- The engineering team spends three months writing flawless, highly optimized code for a feature that is deprecated the week after launch because the market shifted.
- The sales team executes a brilliant, high-touch outbound campaign that books dozens of meetings, only for you to realize the target ICP (Ideal Customer Profile) has zero budget.
- The legal team spends $50,000 drafting a pristine, bespoke intellectual property assignment agreement for an offshore contractor, only for the contractor to ghost before signing.
In the metrics dashboard, the activity looks green. The engineering sprints were completed on time; the outbound emails had a 45% open rate; the legal draft was masterfully executed. But in the real world of cash flow and enterprise value, the utility of these actions is exactly zero.
This is the ultimate founder dilemma: Does an action that is technically perfect but functionally useless still count?
If a process is executed flawlessly but yields no commercial viability, how does the business—and how does the law—evaluate it? Do we judge the action by its internal mechanics (its form) or by its external utility (its outcome)?
This is not a modern software development problem. It is a fundamental metaphysical and legal question debated intensely in the Talmud, specifically in Chullin 85a. The Sages analyze the concept of shechitah she'eina ra'uya—an act of ritual slaughter that is executed with absolute technical precision but is rendered functionally useless because the animal itself is discovered to be terminally flawed (tereifa), or because the context of the act is illicit.
Through this ancient debate, we find a razor-sharp framework for modern corporate governance, product management, and ethical leadership. It forces us to confront the difference between vanity metrics and market-clearing reality, and establishes how we must govern our companies when our best-laid plans yield zero commercial utility.
Full Experience in the App
Listen. Chat. Go deeper.
Audio playback, interactive chevruta, Hebrew tools, and every daily learning track — only in Derekh Learning.
Text Snapshot
MISHNA: In the case of one who slaughters an undomesticated animal or a bird and it is discovered to be an animal with a wound that would have caused it to die within twelve months [tereifa]... Rabbi Meir deems one obligated to cover their blood, and the Rabbis deem one exempt from doing so because, in their opinion, slaughter that is not fit to render the meat permitted for consumption is not considered an act of slaughter.
The Commentary Context
To fully grasp the corporate implications, we must look at how the commentators unpack this tension:
- Rashi on Chullin 85a:1:1:
- Hebrew: אלא ספק איש - ודוחה יום טוב גמור
- Translation: "Rather, it is an uncertain man—and it overrides a full Festival." Rashi highlights that under conditions of absolute structural uncertainty, we are still compelled to take decisive action that carries serious legal consequences.
- Steinsaltz on Chullin 85a:10:
- Hebrew: גמר [למד] בגזירה שווה שחיטה שחיטה משחוטי חוץ... מה התם, בשחיטת חוץ — שחיטה שאינה ראויה לאכילה שמה שחיטה... אף הכא נמי... שחיטה שאינה ראויה שמה שחיטה.
- Translation: "He derives by means of a verbal analogy of 'slaughter' and 'slaughter' from sacrificial animals slaughtered outside the Temple... Just as there, it is a slaughter that is not fit for consumption yet is considered an act of slaughter, so too here... an unfit slaughter is considered an act of slaughter."
- The Ritva on Chullin 85a:3:
- Hebrew: מה לשחוטי חוץ דאי אפשר לעולם בשחיטה ראויה... סוף סוף הא קריא רחמנא שחיטה.
- Translation: "What is unique about slaughter outside the Temple is that it can never be a fit slaughter... yet ultimately, the Merciful One calls it 'slaughter'." The Ritva shows that even when an action is structurally barred from ever producing a positive utility, the action itself retains its formal definition and legal gravity.
- Dor Revi'i on Chullin 85a:2:1-2:
- Hebrew: כיון דושחט קרינן ביה אין דורשין טעמא דקרא וחייב על מעשה השחיטה שעשה... אבל ר"ש דדורש טעמא דקרא סובר... כל שאין המעשה מכשרת לאכילה... מה לי הריגה ומה לי שחיטה.
- Translation: "Since we read 'and he shall slaughter,' Rabbi Meir does not require us to seek the underlying reason of the verse; rather, one is liable for the physical act of slaughter he performed... But Rabbi Shimon, who interprets the underlying reason of the verse, holds: as long as the act does not render the meat fit for consumption, what difference is there between killing and ritual slaughter?" The Dor Revi'i cuts to the core: Are we bound by the literal execution of the process, or does the entire validity of the process depend on its ultimate utility?
Analysis
Insight 1: Relational Liabilities in Failed Operations (The Fairness Principle)
The first major insight of this text addresses how we treat the relational and ethical consequences of our failed business units.
In the Mishnah, we learn about a dispute between Rabbi Meir and the Sages regarding oto ve'et bno—the prohibition against slaughtering an animal and its offspring on the same day Leviticus 22:28. Rabbi Meir holds that if you slaughter an animal, and the slaughter is technically perfect but functionally useless because the animal is a tereifa (unfit for consumption), you are still liable if you slaughter its offspring on the same day.
Why? Because, as Rabbi Yehoshua ben Levi explains in the Gemara, Rabbi Meir derives this from sacrificial animals slaughtered outside the Temple:
"Just as there, with regard to one who slaughters an offering outside the Temple it is a case of slaughter that is not fit to render the meat permitted... and it is nevertheless considered an act of slaughter... so too here... an act of slaughter that is not fit to render the meat permitted is considered an act of slaughter."
The Ritva pushes this further, noting that even though a slaughter outside the Temple can never be valid or fit for consumption, the Torah still designates it as an act of "slaughter" (קריא רחמנא שחיטה).
The Business Parallel
Think of a failed startup pivot or a product line shutdown. You hired a team of fifteen engineers to build a Web3 product. Six months in, the regulatory landscape shifts, or the market evaporates. The venture is dead. It is a commercial tereifa—completely unfit for consumption.
Many founders assume that because the venture was a commercial failure, the standard rules of relational ethics, fair compensation, and professional transition do not apply. They think, "Since we didn't generate any utility, this was just phantom work, and we can wind it down with zero regard for the relational impact."
Rabbi Meir’s position, codified by Rabbi Yehuda HaNasi as the accepted law in this specific case, presents a strict decision rule for founders: The relational and ethical footprint of an action remains fully active even when the commercial utility of that action is zero.
[Flawless Technical Execution] ---> [Zero Market Utility (Tereifa)]
|
+---> [Relational Obligations Remain Active]
| (Severance, IP Clarity, Fair Transition)
If you terminate a team because their project failed, you cannot slash their severance or treat them like lines on a spreadsheet simply because the project yielded no revenue. The act of bringing them on, directing their labor, and ending their employment is still a "slaughter" (a highly consequential corporate action). The ethical liabilities of how you treat those people are not wiped clean by the lack of commercial success.
Decision Rule 1
When decommissioning a failed project, product, or team, the ethical and relational obligations (severance, transition support, IP clarity) must be executed with the same gravity as if the project had been a highly profitable success. A commercial failure does not retroactively excuse poor corporate behavior.
Insight 2: Demolishing Vanity Metrics (The Truth Principle)
The second insight addresses the opposite side of the coin: how we evaluate internal operational progress. Here, the Talmud shifts from the relational prohibition of oto ve'et bno to the positive commandment of kisuy hadam—the obligation to cover the blood of a slaughtered wild animal or bird Leviticus 17:13.
In this case, the Gemara notes that Rabbi Yehuda HaNasi reverses his stance and rules like Rabbi Shimon:
"And he saw as correct the statement of Rabbi Shimon, that ineffective slaughter is not considered an act of slaughter with regard to the mitzva of covering the blood, and taught that halakha in the mishna here using the term: The Sages."
Why does the law treat the covering of the blood differently? Rabbi Shimon’s reasoning is beautifully simple:
"It is written with regard to covering the blood: 'An undomesticated animal or bird that may be eaten,' indicating that the verse is referring specifically to slaughter fit to render the meat permitted for consumption."
The Dor Revi'i explains this divergence masterfully. He argues that Rabbi Shimon is a thinker who "interprets the underlying reason of the verse" (דורש טעמא דקרא). If the entire purpose of the ritual of slaughter is to prepare food for consumption, then an act of slaughter that does not result in edible food is not merely "unfit"—it is structurally disqualified from being called "slaughter" at all. What is the difference, Rabbi Shimon asks, between a highly refined ritual cut that yields inedible meat and simply clubbing the animal over the head? From the perspective of utility, they are identical.
The Business Parallel
This is the ultimate critique of vanity metrics in high-growth startups.
Founders frequently fall in love with "process excellence" at the expense of "market clearance." Your engineering team tells you they successfully completed 100% of their Jira tickets this quarter. Your product team bragged about shipping the new UI. But if those tickets and that UI did not drive activation, retention, or revenue, they did not happen.
Vanity Metric (Rabbi Meir's Process):
[100% Jira Tickets Done] = "We built a great product!"
Market Clearance Metric (Rabbi Shimon's Utility):
[Zero User Retention] = "No actual value was created."
According to Rabbi Shimon, if the meat cannot be eaten, the blood does not need to be covered, because no true "slaughter" occurred. In business terms: If the customer does not derive utility, no work was actually performed.
When you allow your executive team to report on "milestones achieved" without tying those milestones directly to customer utility, you are living in Rabbi Meir’s world of formalistic illusions. You are covering the blood of an animal that was never fit to be eaten.
Decision Rule 2
Decouple operational progress from activity metrics. Define "done" not by the completion of an internal process, but by the measurable validation of market utility. If an initiative does not achieve market clearance, its internal milestone completions are legally and operationally non-events.
Insight 3: Operating Under Structural Uncertainty (The Competition Principle)
The third insight addresses how a business must execute when operating in highly volatile markets where the regulatory or competitive landscape is entirely undefined.
The Gemara opens with a fascinating discussion about the koy (an animal whose status as a wild or domesticated beast is uncertain) and the tumtum (an individual whose biological sex is indeterminate):
"Rather, it must be that the uncertainty in the case of the sounding of the shofar concerns whether a particular individual is a man or a woman, e.g., a tumtum, whose sexual organs are indeterminate... A tumtum is in fact obligated, despite the uncertainty of sex."
We see here a profound legal mechanism for dealing with safek (fundamental uncertainty). The Rabbis do not allow the indeterminate status of the tumtum or the koy to paralyze action. Instead, they construct a framework of "provisional obligation." Because the tumtum might be a man, they are fully obligated to hear the shofar. Because the koy might be a wild animal, its blood must be covered if it is slaughtered on a festival, even though we run the risk of performing an unnecessary labor.
As Rashi notes:
"Rather, it is an uncertain man—and it overrides a full Festival."
The uncertainty does not dilute the operational mandate; it intensifies it.
The Business Parallel
In the early stages of a market—think of generative AI middleware in 2023, or crypto compliance tools in 2020—you are operating in a koy economy. You do not know if your product will be classified as a utility, a security, or a highly regulated enterprise asset.
[Structural Market Uncertainty (The Koy)]
|
+------------------------+------------------------+
| |
[Paralysis / Wait-and-See] [Provisional Obligation]
(Company dies of stagnation) (Execute under worst-case/
best-case scenarios simultaneously)
Many founders respond to this structural uncertainty with paralysis. They adopt a "wait-and-see" posture, waiting for regulators to pass laws or for major platforms to release their APIs.
The Talmudic approach to the tumtum and the koy provides a brilliant competitive decision rule: Uncertainty is not an exemption from execution; it is an operational mandate to build a multi-scenario architecture.
When the status of an asset or market is uncertain, you must assume the maximum burden of compliance and utility. If you are building a fintech product and are unsure if a specific feature will trigger SEC oversight, you do not build it blindly hoping for the best (which is reckless), nor do you stop building entirely (which is fatal). You build the feature with the security and compliance infrastructure required as if it were fully regulated, while maintaining the agility to strip those controls away if it is ruled non-regulated.
Decision Rule 3
When entering an undefined or highly volatile market segment, do not pause execution to wait for market or regulatory clarity. Assume the highest-standard obligation of the most stringent potential scenario, price that compliance cost into your unit economics immediately, and execute without hesitation.
Policy Move
Implement the "Utility-Gate Protocol" (UGP)
To eliminate the massive financial drain of "phantom work" (shechitah she'eina ra'uya) and align your entire organization around functional reality, you must implement a formal corporate policy called the Utility-Gate Protocol (UGP).
This policy permanently divorces executive performance reviews and bonus structures from vanity metrics (e.g., "code shipped," "campaigns launched," "contracts drafted") and ties them exclusively to validated market utility.
[THE UTILITY-GATE PROTOCOL (UGP)]
[Initiation] ---> [Technical Execution] ---> [The Utility Gate] ---> [Value Realized]
|
(Must meet 1 of 3:
- 15% MoM Retention
- $50k ARR Contribution
- 30% Cost Reduction)
|
v
[If Gate Fails: Project
is legally "Unperformed"
for bonus calculations]
The Policy Document
1. Purpose
To transition the company from a culture of activity-based performance (Rabbi Meir’s paradigm) to a culture of utility-based outcomes (Rabbi Shimon’s paradigm).
2. Scope
This policy applies to all product development, engineering sprints, marketing campaigns, and business development initiatives.
3. Protocol Mechanics
No internal project, feature, or campaign shall be designated as "Complete" or "Successful" on any executive dashboard or performance review solely upon the completion of its technical or operational execution phase.
Every initiative must pass through a "Utility Gate" within 90 days of operational launch. To pass the Utility Gate, the initiative must achieve at least one of the following validated market-clearing metrics:
- Product/Engineering: The feature must achieve a minimum of 15% Month-over-Month (MoM) user retention or direct attribution to a closed enterprise deal.
- Sales/Marketing: A marketing campaign must yield a Customer Acquisition Cost to LTV (CAC:LTV) ratio of at least 1:3 within its first cohort.
- Legal/Ops: Any bespoke legal framework or internal tool must demonstrate a verifiable 30% reduction in transaction friction or operating cost.
4. Compensation and Performance Alignment
If an initiative fails to pass its designated Utility Gate within the 90-day window, the initiative is classified as Shechitah She'eina Ra'uya (Ineffective Execution).
For the purposes of quarterly bonus calculations and performance reviews, the hours worked and milestones achieved on that initiative are treated as unperformed.
The executive sponsor’s performance score for that initiative will be marked as zero, regardless of how "flawlessly" the team executed the internal process.
Key Metric to Track: The Utility/Execution Ratio (UER)
To measure the health of your operational efficiency under this policy, the Board must track the Utility/Execution Ratio (UER) as a primary KPI:
$$\text{UER} = \frac{\text{Number of Initiatives that successfully pass the Utility Gate}}{\text{Total Number of Initiatives marked "Executed" by the team}} \times 100$$
- Healthy Target: $> 70%$
- The Danger Zone: $< 40%$ (Indicates your company is wasting massive capital on phantom work—building highly polished, technically sound products that the market does not want or cannot use).
Board-Level Question
"Which of our currently active initiatives are technically compliant with our roadmap but commercially dead, and are we treating the human and relational fallout of those initiatives with the same ethical gravity as our high-revenue divisions?"
This question is designed to pierce through the polished executive presentations that board members typically receive. It forces the executive team to confront the reality of their operations through the dual lenses of Rabbi Meir (relational fairness) and Rabbi Shimon (functional truth).
[BOARD-LEVEL AUDIT FRAMEWORK]
Is the project driving core utility?
/ \
YES NO (Shechitah She'eina Ra'uya)
/ \
[Double down on scale] Are we winding it down ethically?
/ \
YES NO
/ \
[Prudent Capital allocation] [Board Intervention
Required: Ethical
& Legal Risk]
When management presents their quarterly roadmap update, they will show you beautiful green checkmarks indicating that the enterprise software transition is "90% complete," or that the new European expansion office has been "successfully established."
As a board member, your job is to apply the wisdom of Chullin 85a and ask:
- The Utility Audit (Rabbi Shimon): "Yes, the European office is open and the legal entities are established. But has it cleared a single dollar of local revenue? If not, we have performed an ineffective slaughter. Why are we celebrating the opening of an office that has zero market utility? Let us stop tracking 'offices opened' and start tracking 'local customer activation.'"
- The Relational Audit (Rabbi Meir): "If we determine that this European expansion is a commercial tereifa and we must shut it down next month, do we have a transition plan that honors our relational obligations? Or are we planning to quietly terminate those local hires via email with minimal severance because 'the market didn't work out'? We must remember that our ethical liabilities do not disappear when our commercial strategies fail."
By forcing your executive team to answer this two-part question, you establish a culture that is both ruthlessly focused on commercial reality and deeply committed to human dignity.
Takeaway
In the high-stakes world of venture-backed startups, it is incredibly easy to mistake motion for progress.
The profound legal debates of Chullin 85 teach us that activity is not utility.
An act of slaughter that does not yield edible meat is not a slaughter; a line of code that does not serve a user is not a feature; and a corporate partnership that does not generate revenue is not an asset.
As a founder, your mandate is twofold:
- Ruthlessly eliminate vanity metrics. Apply Rabbi Shimon’s standard of utility to your internal operations. If your work does not clear the market, treat it as if it never happened.
- Uphold absolute ethical standards in failure. Apply Rabbi Meir’s standard of relational responsibility to your team. When your initiatives fail—as many inevitably will—you must wind them down with the same fairness, dignity, and generosity as if they had made you a billionaire.
Build with focus. Execute with utility. Exit with honor.
derekhlearning.com