Daf Yomi

Zevachim 60 · Startup voice, On-ramp

November 13, 2025

Hook

Every founder faces the "Damaged Altar" scenario: a core technological asset, proprietary database, or critical manufacturing line fails. The immediate dilemma is not just how to fix it, but what downstream operations must halt immediately. Do you shut down the entire revenue stream, or do you rely on suboptimal, surrounding infrastructure to keep the lights on? This tension defines operational risk tolerance.

This Gemara is a masterclass in defining system dependency. We see Rabbi Elazar rule that if the central processing unit—the Altar—is "damaged" or "lacking," then all dependent value streams (the consumption of offerings) must cease. The cost of running an invalid process outweighs the cost of downtime. But complexity arises with Rabbi Yehuda, who suggests the entire courtyard is consecrated and could theoretically validate service even if the blood spilled on the ground. This introduces the critical distinction between validity (can we still operate?) and optimal performance (should we operate?). When a key asset fails, the ROI calculation hinges on knowing whether your surrounding infrastructure is a legitimate backup or just a distraction that produces tainted output. The Gemara demands we map these dependencies and define the acceptable state of integrity for every component.