Daf Yomi · Startup Mensch · Standard
Chullin 88
Hook
As a founder, your default setting is firefighting. When a catastrophic risk materializes—a massive data breach, a class-action lawsuit, or a co-founder suddenly staging a coup—your survival instincts kick in instantly. You do not need a consultant or an ethics coach to tell you to run from these disasters. They are the operational equivalent of a corpse in the middle of your open-plan office: highly visible, universally avoided, and instantly quarantine-worthy.
The real killers of high-growth startups, however, are not these loud, self-isolating catastrophes. The real killers are the slow, toxic leaks that look completely benign on your daily Slack channels, Jira boards, and Stripe dashboards. It is the high-performing sales executive who hits their quarterly targets but systematically abuses the junior SDRs. It is the slight, almost imperceptible cutting of corners in your product’s data privacy compliance that saves you $10,000 a month in engineering hours but builds up an existential, uninsurable liability.
This is the classic founder’s trap: we over-regulate the obvious, rare disasters while completely ignoring the subtle, daily contamination that we naturally live with.
In the Talmudic discourse of Chullin 88a, the Sages address this exact human bias through the laws of ritual impurity. They analyze why certain sources of impurity require extra rabbinic restrictions while others do not. The distinction they draw is a masterclass in risk management:
"In the case of a zav [an individual with a contagious physical discharge], since people do not naturally separate from him, the Sages decreed additional restrictions with regard to him... In the case of a corpse, since people naturally separate from it, the Sages did not decree additional restrictions with regard to it."
When a risk is so grotesque that your team naturally recoils from it, you do not need heavy compliance overhead. But when a risk is integrated into your daily operations—when the "toxic rockstar" is driving 40% of your revenue—you must build hyper-strict, automated guardrails. If you do not, the daily contact will quietly rot your company from the inside out.
This text challenges us to rethink how we govern our startups. It forces us to ask: Are we wasting our limited governance capital building fences around "corpses" while letting "zavs" run free in our engineering and sales teams? And when we do make mistakes, are we covering them up with expensive, unsustainable PR band-aids, or are we using organic, growth-enabling solutions?
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
What is different with regard to a zav, concerning whom the Sages decreed that liquids that issue from him are ritually impure, and what is different with regard to a corpse, concerning which the Sages did not decree... In the case of a zav, since people do not naturally separate from him, the Sages decreed additional restrictions...
Rabban Shimon ben Gamliel stated a principle: With regard to a substance in which plants grow, one may cover blood with it; and with regard to a substance in which plants do not grow, one may not cover blood with it.
...If one is traveling in the desert... he may grind a gold dinar into powder and cover the blood with it.
— Chullin 88a
Analysis
To build an enduring, venture-backed enterprise, you must transition from reactive firefighting to systemic risk architecture. The Sages’ debates in Chullin 88a regarding ritual containment, the mechanics of "covering up" a slaughter (kisuy hadam), and the raw material constraints of remediation provide three sharp, ROI-minded decision rules for modern founders.
Insight 1: The "Zav" Rule of Operational Governance (Fairness & Risk Containment)
In the startup ecosystem, we routinely misallocate our compliance and monitoring resources. We write exhaustive, multi-page employee handbooks outlawing extreme, cartoonish behaviors that no reasonable person would ever commit, yet we remain silent on the grey-area behaviors that occur every single day.
The Gemara asks a fundamental structural question: Why did the Sages impose harsher, precautionary decrees on the bodily fluids of a zav than on the fluids of a corpse? A corpse is the ultimate source of impurity (avi avot hatumah), whereas a zav is a lesser degree of impurity (av hatumah).
The answer is profoundly practical:
"In the case of a zav, since people do not naturally separate from him, the Sages decreed additional restrictions... In the case of a corpse, since people naturally separate from it, the Sages did not decree..."
Because a corpse is obviously dead, human beings naturally keep their distance. There is no risk of casual, accidental contamination. But a zav is alive, walking among the community, conducting business, and eating at the communal table. Because "people do not naturally separate from him," the risk of systemic, invisible contamination is extraordinarily high. Therefore, the Sages built an aggressive regulatory fence around him.
Rashi, in his commentary on this passage, notes:
"ואלו ואלו אין מטמאין - דלא גזור בהו רבנן טומאה" ("These and those do not impart impurity—because the Sages did not decree impurity upon them" Rashi on Chullin 88a:1:1)
This highlights that rabbinic intervention is not a theoretical exercise in holiness; it is a targeted, behavioral intervention designed to mitigate real-world human error.
As a founder, your "corpse" risks are things like blatant intellectual property theft, physical violence, or wire fraud. You do not need to spend precious cycles writing policies for these; the law, social norms, and basic human self-preservation naturally keep your employees away from these cliffs.
Your "zav" risks are the high-performing, culturally toxic individuals. It is the brilliant engineer who refuses to document their code, mocks junior developers in public Slack channels, but is kept on because "only they know how the legacy database works." Because this person is alive, highly productive, and integrated into your daily sprint cycles, your team does not naturally separate from them. They tolerate the toxicity because they want to hit their shipping dates.
The Decision Rule: You must apply your strictest operational guardrails and zero-tolerance policies not to the extreme, unimaginable catastrophes, but to the highly integrated, daily risks that your team is naturally tempted to tolerate. If a behavior is toxic but highly productive, you cannot rely on "organic" cultural self-regulation. You must implement automated, structural boundaries (such as peer-review mandates, mandatory documentation redundancy, and 360-degree cultural reviews tied directly to equity vesting) to prevent the contagion from ruining your engineering velocity and team retention.
Insight 2: The "Plant-Growing" Principle of Remediation (Truth & Sustainable Recovery)
Every startup will eventually spill blood. You will ship a buggy release that corrupts customer data, violate a vendor contract, or accidentally mislead your investors during a cash-crunch bridge round. The question is not whether you will make mistakes, but how you "cover" them.
The Torah commands that after slaughtering a wild animal or bird, one must cover its blood: "And he shall cover it with earth" Leviticus 17:13. The Mishnah in Chullin 88a immediately enters a granular debate about what materials are valid for this covering.
Rabban Shimon ben Gamliel provides a brilliant, unifying operational principle:
"With regard to a substance in which plants grow, one may cover blood with it; and with regard to a substance in which plants do not grow, one may not cover blood with it."
This is not merely an agricultural detail; it is an ethical blueprint for corporate remediation. When you have an operational failure (a "spill"), you are legally and ethically obligated to cover it—to contain the damage and protect your stakeholders. But how do you cover it?
Do you cover it with "thick sand," "filings of metal vessels," or "fine chaff of flax" that has been chemically treated? In the startup world, these are the equivalents of non-disclosure agreements (NDAs), aggressive PR spin, and throwing cash at disgruntled customers to buy their silence. These materials are sterile. They cover the mess, but nothing can ever grow there again. You have created a dead zone in your company's culture and operations.
The Sages insist that the covering must be done with "earth" (afar), specifically a medium that is fertile. Steinsaltz, in his commentary on this passage, explains that the substance must have the organic properties of soil:
"...שחיקת חרסית, ונעורת פשתן דקה..." ("...crushed potsherd, and fine sawdust of carpenters, and fine chaff of flax..." Steinsaltz on Chullin 88a:10)
These are organic materials that decompose, integrate with the earth, and ultimately foster new life.
Consider the extreme edge case presented in the Gemara:
"If one is traveling in the desert... and he does not have dirt... he may grind a gold dinar into powder and cover the blood with it."
Grinding a gold dinar to cover blood is the ultimate corporate tragedy. It represents a founder destroying valuable, hard-earned capital (your runway) to resolve an ethical or operational failure that could have been prevented or handled through healthy, organic processes. Yes, it is halachically valid in an absolute desert emergency, but it is a massive, value-destroying waste of resources.
The Decision Rule: When rectifying a major company error, your remediation strategy must be "fertile," not merely cosmetic. If your post-mortem of a product failure consists of a slick PR statement and a one-time customer credit (grinding a gold dinar), you have wasted your capital. A fertile remediation requires a transparent root-cause analysis, an open-source post-mortem shared with your community, and a structural change to your codebase or team training. You must cover your mistakes with "soil" that allows trust, engineering maturity, and brand equity to grow back stronger.
Insight 3: The "Blood of the Soul" vs. "Spurted Blood" (Competition & Resource Prioritization)
One of the greatest threats to a startup’s survival is compliance paralysis. If you treat every minor operational hiccup, every slightly delayed vendor payment, or every trivial user interface bug as an existential ethical crisis, your competitors will run circles around you. You will bleed out your runway while agonizing over insignificance.
The Sages debate exactly which blood must be covered under the biblical commandment:
"The Rabbis hold that the expression: 'Its blood' (Leviticus 17:13), indicates an obligation to cover all of its blood, even the blood that spurts out... And Rabban Shimon ben Gamliel holds that 'its blood' refers to the special blood, i.e., the blood of the soul."
The "blood of the soul" (dam hanefesh) is the life-giving, concentrated blood that flows at the moment of slaughter—the vital essence of the animal. The "spurted blood" (dam hatizuz) is the incidental spray that hits the walls or the knife during the process. Rabban Shimon ben Gamliel argues that once you have covered the core, life-giving blood, you are completely exempt from chasing down every single microscopic droplet that sprayed onto the surrounding environment.
In his commentary, Rabbeinu Gershom emphasizes this focus on the core source:
"...משקין היוצאין ממנו כמשקין הנוגע בהן... אע"פ שהמת אבי אבות הטומאה..." ("...the liquids that issue from it are like the liquids that touch it... even though a corpse is the ultimate father of impurity..." Rabbeinu Gershom on Chullin 88a:1)
He highlights the distinction between the primary source of impurity and the secondary, accidental contacts.
In a fast-growing startup, you must distinguish between the "blood of the soul" of your business and the "spurted blood." The blood of the soul is your core integrity: the absolute security of your users' private data, the accuracy of your financial reporting to your board, and the fundamental safety and dignity of your workplace culture. If you compromise on these, your company dies. The soul departs.
The "spurted blood" consists of the inevitable, messy side effects of rapid scaling: a minor SLA breach with a non-enterprise client, a typo in your terms of service that has no practical legal impact, or a temporary system downtime of 15 minutes during a scheduled maintenance window.
If you apply the same bureaucratic, heavy-handed "covering" process to these minor spurts as you do to the core life-force of your business, you will destroy your engineering velocity and kill your company's competitive edge.
The Decision Rule: Establish a clear, two-tiered triage system for operational and ethical issues. Tier 1 ("Blood of the Soul") represents core systemic vulnerabilities, cultural misconduct, or legal fraud; these require immediate, absolute, and publicly accountable remediation. Tier 2 ("Spurted Blood") represents non-systemic edge cases, minor bugs, and operational friction; these must be logged, addressed via standard operating procedures, and resolved without triggering a full-scale corporate crisis response. Do not burn your gold dinars trying to cover up the dust of daily operations.
STARTUP RISK MATRIX
(Based on Chullin 88)
High | -------------------------------------------------
| "ZAV" RISKS | "CORPSE" RISKS
| (Integrated, Daily Rot) | (Obvious Crises)
| |
| * Toxic High-Performer | * Blatant Fraud
| * Grey-Area Billing Practices | * IP Theft
| * Un-documented Legacy Code | * System Melt
Operational | |
Integration Low | -------------------------------------------------
| "SPURTED BLOOD" | "GOLD DINAR"
| (Incidental Spray) | (PR Cash Burn)
| |
| * Minor SLA Breaches | * Buying Silence
| * Non-critical Bugs | * Non-Fertile NDAs
| * Typos in Terms of Service | * Brand Band-Aids
| |
-----------------------------------------------------------
Low High
Potential for Growth
Policy Move
The "Soil vs. Gold" Incident Response and Remediation Framework
To turn these ancient insights into immediate, venture-scale ROI, you must eliminate the standard, reactive "PR-first" crisis management playbook. Instead, you will implement a structured, automated "Soil vs. Gold" Incident Response Policy.
This policy mandates that every post-mortem of a corporate failure (whether it is an engineering outage, a sales compliance breach, or an HR dispute) must categorize the proposed fixes and measure their long-term viability using a specific metric: the Remediation Growth Index (RGI).
REMEDIATION GROWTH INDEX (RGI)
Systemic, Automated, Growth-Oriented Actions (Soil)
RGI = -----------------------------------------------------
Manual, Non-Growth, Cosmetic Capital Burn (Gold)
* Target: RGI > 2.0 (High-growth, sustainable recovery)
* Warning: RGI < 1.0 (Sterile, expensive, capital-wasting cover-up)
1. Categorization of Remediation Actions
Every action item generated in a post-mortem must be classified as either Soil or Gold/Thick Sand:
- Soil Actions (Valid Coverings):
- Automated codebase fixes (e.g., writing integration tests to prevent a recurring bug).
- Structural, peer-reviewed policy changes (e.g., establishing a dual-authorization system for financial transfers).
- Transparent, public-facing root-cause analyses shared with customers or the open-source community.
- Upskilling programs or internal role reassignments to address a systemic skill deficit.
- Gold/Thick Sand Actions (Invalid/Sterile Coverings):
- Manual, human-dependent review steps that slow down velocity without solving the root cause (e.g., "The VP must now manually approve every single pull request").
- One-time customer credits, discounts, or cash payouts designed to prevent churn without fixing the product (grinding the gold dinar).
- Legal threats, NDAs, or aggressive PR spin designed to bury the story rather than resolve the underlying failure.
2. The Remediation Growth Index (RGI) Metric
The RGI is calculated as follows:
$$\text{RGI} = \frac{\text{Sum of Estimated Engineering/Operational Hours Allocated to "Soil" Actions}}{\text{Sum of Direct Capital Outlay + Opportunity Cost of "Gold/Thick Sand" Actions}}$$
- The RGI Threshold: No post-mortem can be closed, and no incident report can be signed off by the Executive Team, unless the proposed remediation plan achieves an RGI of > 2.0.
- The Goal: This ensures that for every dollar or hour spent on temporary, cosmetic containment (Gold), the company is investing at least double that resource into building permanent, automated, growth-enabling systems (Soil).
3. Execution Workflow
When an incident is declared:
- Isolate the "Blood of the Soul": The incident response team must immediately isolate the core threat to data, financial solvency, or physical safety.
- Draft the Post-Mortem: Within 48 hours of resolution, the team drafts a post-mortem detailing the root cause.
- Calculate the RGI: The proposed action items are mapped to the RGI formula. If the RGI is below 2.0—meaning the company is simply throwing cash or manual bureaucracy at the problem—the plan is rejected. The engineering and operations teams must return to the drawing board to design automated, systemic, and educational solutions that allow the company to grow from the crisis.
- Board Notification: Any incident that requires "Gold" spending exceeding $50,000 (such as legal settlements or customer SLA payouts) must be reported to the Board of Directors along with the corresponding "Soil" engineering plan.
Board-Level Question
Are we over-indexing our risk management on highly visible "corpses" while ignoring the active, high-performing "zavs" in our daily operations?
To ask this question effectively at your next board meeting, you must challenge the traditional, check-the-box corporate governance model. Most boards of directors evaluate risk through a sterile, lagging-indicator lens: they review completed audits, glance at high-level financial controls, and ensure the company has adequate D&O (Directors and Officers) insurance.
This is the equivalent of verifying that there are no "corpses" in the boardroom. It is necessary, but it is fundamentally insufficient for a high-growth startup.
You must bring the logic of Chullin 88a to your board. Explain to them that the most dangerous liabilities on your balance sheet are not the black-swan events, but the active, culturally integrated risks that your executive team is highly incentivized to tolerate.
To operationalize this question, present your board with the following diagnostic matrix:
BOARD-LEVEL RISK AUDIT
Obvious "Corpse" Risks Active "Zav" Risks
(Naturally Separated) (Highly Integrated)
---------------------- -------------------
* Standard SOC 2 Audits * Key-Person Code Dependencies
* General Liability Insurance * High-Churn Engineering Teams
* Basic Financial Audits * Toxic Revenue-Generating Execs
* Standard Legal Templates * Grey-Area Sales Incentives
Use this framework to guide the board through a deep, qualitative review of your operational reality. Address three specific vectors of integrated risk:
1. The Key-Person Dependency (Operational Zav)
- The Reality: Do we have a brilliant, highly volatile technical founder or lead architect who refuses to document their work, locks down access to production environments, and treats colleagues with contempt?
- The Board's Role: Because this person is keeping the product alive, the executive team will naturally avoid separating from them. The board must demand a structured, time-bound technical redundancy plan. This is not about firing the key person; it is about building the necessary "rabbinic fences" (such as automated testing, mandatory code pairing, and decentralized access controls) to ensure that if this person leaves or burns out, they do not take the company's entire enterprise value with them.
2. The Toxic Rainmaker (Cultural Zav)
- The Reality: Is our top-performing sales executive or growth marketer responsible for 35% of our pipeline but also responsible for 80% of our HR complaints?
- The Board's Role: In the early stages, boards are highly tempted to ignore these cultural red flags because they want to preserve the top-line growth curve for the next funding round. But this is a classic "zav" contagion. The toxic behavior of a senior leader silently destroys the morale, performance, and retention of your broader team, leading to massive, unhedged replacement costs down the road. The board must insist on clear, non-negotiable clawback provisions in executive equity agreements and tie performance bonuses directly to cultural and retention metrics.
3. The Technical and Regulatory Arbitrage (Compliance Zav)
- The Reality: Are we accelerating our product launch by relying on grey-area data scraping, loose consent flows, or non-compliant contractor classifications?
- The Board's Role: This is not a "corpse" risk—it won't shut you down tomorrow. It is an integrated "zav" risk. It allows you to show impressive week-over-week user growth, which pleases the board in the short term, but it builds a massive, systemic compliance debt. When a Tier 1 institutional investor conducts due diligence for your Series B or C round, they will discover this rot, and it will drastically slash your valuation or kill the deal entirely. The board must actively monitor and audit your compliance debt, treating it with the same financial rigor as your cash burn rate.
By asking this question and reframing risk around the "Zav" principle, you shift your board's posture from passive, defensive oversight to active, strategic value creation. You ensure that your governance is designed to protect the soul of the company, rather than just checking boxes on an insurance form.
Takeaway
True startup ethics are not about theoretical purity; they are about sustainable operational design.
As Chullin 88a teaches, we must stop wasting our scarce governance capital on obvious "corpses" that the team naturally avoids. Instead, we must build rigorous, automated guardrails around our highly integrated "zav" risks—the productive but toxic behaviors we are most tempted to tolerate.
When failures occur, we must reject the sterile, expensive "gold dinar" cover-ups of PR spin and legal NDAs. We must cover our mistakes with the "soil" of transparent, automated, and growth-oriented systems that allow our culture and our product to sprout back stronger.
Protect the soul of your business, automate your boundaries, and build a fertile foundation for venture-scale growth.
derekhlearning.com