Daily Mishnah

Mishnah Oholot 14:5-6 · Startup voice, On-ramp

November 1, 2026

Hook

In the startup ecosystem, we are obsessed with "edge cases"—those freak events that threaten to break our architecture. Founders often operate under the delusion that if a problem is sufficiently niche, or if the "surface area" of the risk is small enough, it doesn’t exist for the purposes of the roadmap. We convince ourselves that our legal exposure, our toxic cultural debt, or our technical shortcuts are "insignificant" because they only trigger under specific, highly improbable conditions.

But here is the hard truth: in the world of systems, the exception is the rule. If a flaw exists, it acts as a conductor. The Mishnah in Mishnah Oholot 14:5 deals with complex spatial relationships—projections, balconies, and the way uncleanness "travels" through physical space based on its proximity to structural features. It forces us to confront a brutal reality: your "small" failures are never contained. Whether it’s a corner-cutting product update or a misalignment in your cap table, these structural "projections" function as conduits. They carry the "uncleanness" (the systemic risk) across your entire organization. You think you’ve isolated the problem to the "basement," but the structure of your company is rigged to propagate that risk to the "sky." You aren’t just managing a business; you are maintaining a system of connectivity. The question isn't whether your shortcuts will cause damage; it's how wide the conduit is.

Text Snapshot

"A projection brings uncleanness, whatever width it may be... When higher than that, it brings uncleanness only if it is one handbreadth wide. Cornices and carvings bring uncleanness when they are one handbreadth wide... If the upper [projection] overlapped the lower to the extent of one handbreadth... what is beneath and between them becomes unclean." Mishnah Oholot 14:5-6

Analysis

Insight 1: Proportionality is a Trap

The text distinguishes between different types of architectural projections and their thresholds for transmission. Rabbi Yose and others debate when a projection is merely decorative (a cornice) and when it is a functional "bridge" for impurity. In business, founders often employ "threshold thinking": If the risk is less than 5% of revenue, we don’t need a policy. This is the logic of the cornice. However, as the Mishnah notes, "A projection that is above a doorway forms a passage for the uncleanness when it is one handbreadth wide" Mishnah Oholot 14:5.

Decision Rule: Never evaluate risk based on current volume; evaluate it based on connectivity. If a process creates a potential "passage" for a cultural or technical failure, the size of the initial incident is irrelevant. A small, recurring oversight in your code review process is a "one handbreadth" conduit. It might seem small today, but if it connects the "doorway" (your customer-facing interface) to the "house" (your core infrastructure), the infection will spread. Do not measure the risk by the weight of the current error; measure it by the breadth of the channel you have inadvertently created.

Insight 2: The Logic of Overlap and Cumulative Risk

The later sections of the text regarding "two projections, one above the other" Mishnah Oholot 14:6 demonstrate how risk intensifies when structural elements overlap. When two compromised elements align, the "impurity" isn't just shared; it becomes a locked-in state. As Rash MiShantz explains, if the projections are aligned ("like the beams of a house and an upper story"), the transmission is absolute.

Decision Rule: When you stack processes, you are stacking risks. If you have a broken hiring process (a projection) and a broken performance review system (a second projection), and these two overlap in your HR software, you haven’t just doubled your risk; you’ve created a permanent conduit for toxic culture. You must audit your systems for "spatial overlap." Where does your customer support feedback loop overlap with your product development cycle? If both are "unclean"—meaning inefficient or misaligned with company values—that overlap is the exact point where you will experience total system failure.

Insight 3: The "Uncleanness Cleaves" (The Persistence of Debt)

The text concludes with a terrifying realization: "If they did not have a width of a handbreadth... if there is uncleanness beneath, between or above them, the uncleanness cleaves upwards and downwards" Mishnah Oholot 14:6. This is the definition of Technical or Cultural Debt. When your systems are not sufficiently robust, the "uncleanness" ceases to be localized. It becomes atmospheric. It fills the room.

Decision Rule: You cannot "contain" bad practices in a silo. If you ignore a compliance issue or a toxic manager because they are "contained" in a small department, you are violating the fundamental reality of systemic physics. Debt is not a box; it’s a gas. It will expand to fill the available space. If your leadership team is "unclean," the entire company becomes unclean. The "uncleanness cleaves." You cannot stop it through containment; you can only stop it through removal (purification).

Policy Move

Implement a "Conduit Audit" in your quarterly OKR review. Most companies measure output (KPIs). You will start measuring Systemic Transmission Velocity (STV).

  • The Process: Every department head must identify one "Projection"—a shortcut or structural compromise currently in use (e.g., "we bypass security protocols to deploy patches faster").
  • The Metric: Determine the "Handbreadth" of that projection. If it connects two major systems (e.g., the production database and the unprotected test environment), it is a "One Handbreadth" violation.
  • The Mandate: Any projection with a "width of one handbreadth" must be closed or structurally separated within 30 days. No excuses. Use the following KPI: Number of High-Transmission Conduits (HTC). An HTC is any system bridge that bypasses standard compliance or quality controls. Your goal is to keep the HTC count at zero. If the count is above zero, your technical debt is not a "risk"—it is a planned failure.

Board-Level Question

"We have spent this quarter focused on the growth of our top-line metrics. I want to shift the focus to our structural 'projections.' Which of our internal processes currently act as a conduit for 'uncleanness'—where a single point of failure in one department would, by design, infect the entire organization's operational integrity? And more importantly, which of these are we 'tolerating' simply because we've convinced ourselves they are below the threshold of importance?"

Takeaway

The Mishnah teaches that you are not just a collection of departments; you are a single physical structure. Risks are not localized incidents; they are signals moving through a circuit. Your job as founder is not to build the biggest house, but to ensure that your house is not designed to distribute the very rot that will inevitably pull it down. Stop measuring the size of the hole; start looking at what the hole is connected to. Containment is a myth; architectural integrity is the only defense.