Daily Rambam Accelerated

Mishneh Torah, Defilement of Foods 10-12

Bite-SizedSeptember 17, 2026

Hook

Founders obsess over "product-market fit," but often ignore "intent-impact fit." You build features, hire teams, and burn cash, assuming your intentions—"we're building for good"—shield you from the messiness of execution. The Torah warns: Your intent matters, but reality creates its own liability.

Text Snapshot

"It applies only when the crops were exposed to the liquids willfully by the owner after the crops were uprooted from the earth... If the food was exposed to liquids against his will, it does not make them susceptible to impurity." Mishneh Torah, Defilement of Foods 12:1, 12:3

Analysis

1. The Agency of "Willful" Action

The law hinges on whether the contact between liquid and food was willful. In business, this is your "conscious design." If you knowingly let your product touch "impure" environments (bad partnerships, unethical data practices), you own the contamination. If it happens by accident or necessity, the legal—and moral—liability is fundamentally different.

2. The Liability of Passive Acceptance

Even if you didn't initiate the contact, if you desired the outcome, you are liable. The text notes that if an owner is ultimately pleased by a liquid touching their food, it becomes susceptible to impurity Mishneh Torah, Defilement of Foods 12:3. If you benefit from a "dirty" process—even if you claim you didn't set it up—your consent to the result makes you responsible.

3. Separation from the Source

Liquids still connected to the "ground" (the status quo/baseline industry standards) are often neutral. Once you "uproot" them—by taking them into your private startup ecosystem—they become your responsibility. You cannot claim "that's just how the industry works" once you have pulled those practices into your own operations.

Policy Move

The "Intent Audit": Implement a quarterly review where product managers must document the "willful" vs. "accidental" nature of third-party data or supply chain interactions. If a process is "unavoidable," explicitly document the lack of intent to benefit from its "impurity" (e.g., non-compliant sourcing).

Board-Level Question

"Are we benefiting from processes or data sources that we would be embarrassed to defend as a 'willful' choice if they were brought into the public light?"

Takeaway

Your product inherits the "impurity" of the systems you intentionally allow it to touch. Stop hiding behind "industry standards"—if you’ve uprooted them and brought them into your house, you own the contamination.

KPI Proxy: % of third-party vendor interactions categorized as "Operational Necessity" vs. "Strategic Choice."