Zevachim 112

Hook

You’ve pivoted. You’ve killed projects. You’ve retired features. But as a founder, you know the truth: nothing truly dies. That "dead" code still consumes server space, that "retired" product still generates support tickets, that "shelved" project still ties up mental bandwidth. The question isn’t if it’s dead, but what kind of dead it is. Is it truly gone, no liability, no lingering consequence? Or is it merely a "remainder," still capable of biting you, still demanding proper burial – or, worse, still carrying a hidden potential you're ignoring?

This isn't just about technical debt; it's about strategic debt. Every decision to move on leaves a wake. Do you understand the difference between an asset that’s truly disqualified from its original purpose (and thus carries no further penalty for its misuse) versus one that’s merely a remainder (and thus still subject to rules, still carrying liability)? Mismanaging this distinction costs you time, money, and focus. You're either wasting resources on the truly dead, or negligently discarding something that still holds value or, more importantly, liability.

The Gemara, in Zevachim 112, dives deep into this exact dilemma with sacrificial offerings. It's an ancient text, but its ROI-minded clarity on "fitness for purpose" and the nuanced liabilities of "remainders" versus "disqualified" assets is a masterclass in strategic resource management. Let's unearth the wisdom.

Text Snapshot

The Gemara discusses the liability for offering blood outside the Temple courtyard:

• "As the blood in its entirety is fit to be placed inside the courtyard. But in a case where he first placed its blood on the altar inside the courtyard and then offered up the remaining blood on an altar outside the courtyard, why he is liable? That blood is merely a remainder, and one should not be liable for offering it up outside." (Zevachim 112a)
• "For any offering that is not fit to come to the entrance of the Tent of Meeting for sacrifice on the altar... one is not liable for its slaughter and sacrifice outside its place." (Zevachim 112b)
• "But if one separated two sin offerings from the outset as a guarantee, so that even if one is lost he can use the other, then if neither is lost and he sacrifices one of them... from the outset, one of these two animals... is a burnt offering, and therefore if one offers it up outside the courtyard he is liable." (Zevachim 112a)
• "With regard to doves whose time of fitness has not arrived; and pigeons whose time of fitness has passed, that one sacrificed outside the Temple courtyard, he is exempt. Rabbi Shimon says: For pigeons whose time of fitness has passed one is exempt, and for doves whose time of fitness has not yet arrived he is in violation of a prohibition." (Zevachim 112b)
• "Until the Tabernacle was established, private altars were permitted... And from the time that the Tabernacle was established, private altars were prohibited." (Zevachim 112b)

Analysis

This text provides a powerful framework for assessing asset lifecycle, liability, and strategic resource allocation in your startup. It forces a rigorous distinction between what's truly dead and what's merely dormant, and how those distinctions impact your "liability" – whether that's legal, financial, or opportunity cost.

Insight 1: The Critical Distinction: "Remainder" vs. "Disqualified" Liability

The Gemara hinges on a crucial differentiation: is an item merely a "remainder" (שיריים), or is it truly "disqualified" (דחוי)? The consequence for misusing a "remainder" is liability, whereas for a "disqualified" item, there is no liability.

Consider the case of the two cups of blood from a sin offering: if one cup is used inside, and the "remaining" blood from the same offering is offered outside, the person is liable. The Gemara asks, "That blood is merely a remainder, and one should not be liable for offering it up outside?" The answer from Rabbi Neḥemya is a resounding "liable." This teaches us that a "remainder" isn't inert; it still carries the weight of its original designation and the rules governing it.

However, the mishna then presents a scenario with "two cups" where "if he first placed the blood from one cup inside and then placed the blood from the other one outside, he is exempt." Why? Because using the first cup "rendered the blood in the second cup a mere remainder." But then the Gemara argues this must be according to a different opinion, where "The placement of the blood from one cup renders the blood of the other cup as disqualified." (Zevachim 112a, as explained by the first tanna disagreeing with Rabbi Elazar, son of Rabbi Shimon). The key is that disqualification (דחוי) frees one from liability.

Founder's Takeaway: Many of your "retired" products, "deprecated" features, or "shelved" projects are not truly disqualified. They are remainders. They still carry the potential for unexpected liabilities, maintenance costs, or even legal obligations.

• "Remainder" Assets: These are partially completed projects, old product versions, or even team members performing secondary roles. They still possess some inherent "fitness" or connection to an active purpose. Mismanaging them (e.g., offering them "outside" your core strategy) still incurs "liability" – wasted effort, technical debt, reputational damage.
• "Disqualified" Assets: These are truly obsolete, permanently non-viable projects, or features that no longer serve any purpose. Once formally disqualified, you're "exempt" from liability for their misuse because they are inherently unfit for any relevant purpose.

Decision Rule: Before decommissioning an asset or project, clearly categorize it as "Remainder" or "Disqualified." If it's a "Remainder," understand that it still requires strategic handling and can incur "liability" if misused. If it's "Disqualified," you have the freedom to truly let go without ongoing penalty.

Insight 2: The Truth Test: Is it "Fit to Come to the Entrance"?

The bedrock principle for exemption from liability is whether an item is "fit to come to the entrance of the Tent of Meeting." The Mishna explicitly states: "For any offering that is not fit to come to the entrance of the Tent of Meeting for sacrifice on the altar... one is not liable for its slaughter and sacrifice outside its place." (Zevachim 112b). It then lists numerous examples of inherently unfit items: the red heifer (burned outside its pit), the scapegoat (cast off a cliff), animals involved in bestiality, animals set aside for idol worship, blemished animals, tereifa (animals with a fatal wound), and more.

Founder's Takeaway: This is your "Go/No-Go" gate. Before allocating resources or continuing efforts, ruthlessly ask: Is this truly "fit to come to the entrance"? Is this product, feature, or strategy inherently fit for its core purpose in our current market?

• Objective Fitness: The text describes animals "that copulated with a person" or "was worshipped as a deity." These are inherently, fundamentally unfit. They cannot fulfill the sacred purpose. Similarly, a product built on obsolete tech, a feature lacking market fit, or a strategy misaligned with your core mission are inherently "unfit." Stop trying to make them "fit."
• No Liability for the Unfit: The Mishna explicitly states, "one is not liable for its slaughter and sacrifice outside its place." This implies that if something is truly unfit, you are not penalized for treating it as such, even if that means "slaughtering it outside" (e.g., publicly deprecating a feature, killing a product line). In fact, trying to force an unfit item into a fit role is where real liability arises.

Decision Rule: Establish clear, objective criteria for "fitness for purpose" for all major initiatives. If an asset or project objectively fails these criteria (like a tereifa animal), recognize it as "unfit" and expedite its formal "disqualification." Don't incur ongoing "liability" (wasted resources, opportunity cost) trying to make the inherently unfit "fit."

Insight 3: The Imperative of Strategic Agility & Timing

The text highlights two critical dimensions of fitness: timing and context.

First, timing: "With regard to doves whose time of fitness has not arrived; and pigeons whose time of fitness has passed... he is exempt." (Zevachim 112b). Rabbi Shimon then adds nuance, distinguishing between "a prohibition" and karet liability for the premature dove. The takeaway is clear: even if an item could be fit, its fitness is time-bound. A product launched too early (doves whose time has not arrived) or too late (pigeons whose time has passed) is considered "unfit" for its current purpose, leading to exemption from liability for external sacrifice. This doesn't mean it's worthless, but it's not currently viable for its primary role.

Second, context: "Until the Tabernacle was established, private altars were permitted... And from the time that the Tabernacle was established, private altars were prohibited." (Zevachim 112b). This isn't just a historical footnote; it’s a profound lesson in adapting to new market conditions, regulatory environments, or organizational stages. What was permitted (and even holy) in one context becomes prohibited and incurs severe liability in another. The rules of engagement change.

Founder's Takeaway: Your market, technology, and organizational maturity are constantly shifting. What was "fit" last year may not be "fit" today. What's "fit" for an early-stage startup might be a liability for a scaled enterprise.

• Launch Timing is Everything: Don't launch "doves" before their time – avoid premature scaling, over-engineering, or releasing features before market readiness. And don't cling to "pigeons" whose time has passed – sunset old tech, retire dated features, or pivot from stale strategies without sentimentality.
• Context Dictates Rules: The rules for "private altars" changed dramatically based on the stage of national development (Tabernacle, Shiloh, Jerusalem). Your startup's "altars" (e.g., growth strategies, operational models, sales channels) have rules that evolve with your stage. What was acceptable (or even necessary) at seed stage (e.g., "growth hacking" tactics, informal processes) becomes prohibited and potentially destructive at Series B.

Decision Rule: Implement a regular "Fitness & Context Review" for core strategies, products, and processes. Assess not just if something is fit, but when (is its time now?) and where (is it appropriate for our current stage/market?). Be prepared to adapt or decommission based on these time- and context-sensitive fitness assessments.

Policy Move

Policy: The "Asset Lifecycle & Liability Framework" (ALL-F)

We will implement a mandatory, quarterly review for all significant product features, strategic initiatives, and technology stacks that fall outside the "actively growing" category. The goal is to rigorously classify these assets and manage their associated liabilities.

Process:

1. Inventory & Categorization: For each asset, classify it into one of three categories:

   • "Active & Fit": Actively supported, growing, and "fit to come to the entrance" (i.e., serving its primary strategic purpose effectively). This category requires continuous investment.
   • "Remainder & Managed": No longer "Active & Fit" but still possessing inherent potential or carrying residual obligations. This aligns with the Gemara's "remainder" concept (e.g., "That blood is merely a remainder, and one should not be liable for offering it up outside?" – yet liability exists!). These assets are not fit for their original purpose but are still fit for a secondary, defined purpose (e.g., legacy support, data archive, repurposing for a new project).
     • Action: Define a clear, time-bound management plan. This includes minimal maintenance, data migration, potential repurposing, and a path to eventual "Disqualification."
     • Liability: These assets still incur liability (cost, security risk, opportunity cost). They are "in violation of a prohibition" (Rabbi Shimon's view on "doves whose time has not arrived" – Zevachim 112b).
   • "Disqualified & Decommissioned": Inherently and permanently unfit for any strategic purpose, carrying no residual value or unavoidable obligation. This aligns with the Mishna's "For any offering that is not fit to come to the entrance of the Tent of Meeting... one is not liable for its slaughter and sacrifice outside its place." (Zevachim 112b).
     • Action: Full decommissioning, archival, and resource reallocation. No further active investment or management is required.
     • Liability: Minimal to none, as it's truly "exempt."

2. Decision-Making Protocol:

   • "Active & Fit" -> "Remainder & Managed": Requires a clear "sunsetting" plan, approved by product and engineering leadership.
   • "Remainder & Managed" -> "Disqualified & Decommissioned": Requires explicit sign-off from relevant department heads (e.g., legal for data retention, engineering for infrastructure, product for customer impact). This ensures all potential "liabilities" are addressed before true "exemption."

KPI Proxy: "Strategic Debt Ratio": (Total estimated annual cost of "Remainder & Managed" assets / Total annual R&D budget). Our goal is to keep this ratio below 10% to ensure we are not unduly burdened by past initiatives and are effectively transitioning assets. This measures our efficiency in managing "remainders" before they become liabilities.

Board-Level Question

"Given our aggressive growth targets and the rapid pace of market evolution, what is our leadership's current assessment of our 'organizational fitness for purpose'? Specifically, how are we rigorously defining and regularly auditing the 'fitness' (as per the principle of 'fit to come to the entrance' – Zevachim 112b) of our current product portfolio, strategic initiatives, and key talent pools against today's market realities and our current stage as an organization? And what is our estimated 'Strategic Debt Ratio' (cost of 'Remainder & Managed' assets / R&D budget) for the next fiscal year, ensuring we're not carrying undue 'liability' from past initiatives or failing to adapt to the changing 'rules of altars' that define our competitive landscape?"

Takeaway

The Gemara on Zevachim 112 isn't just about ancient rituals; it's a foundational text for ruthless resource allocation and liability management. Don't be fooled by "dead" projects; understand if they are mere "remainders" (still liable) or truly "disqualified" (exempt). Ruthlessly assess "fitness for purpose" for all assets, adapting to current context and timing. Your ROI depends on it.