Daily Rambam Accelerated · Startup Mensch · On-Ramp
Mishneh Torah, Tithes 13-14
Hook
Founders are obsessed with "product-market fit," but they rarely talk about "supply-chain integrity." You spend months auditing your tech stack, checking for open-source vulnerabilities, and vetting your cloud providers, but how much do you know about the provenance of your operational inputs? In the early stages, you are often buying from "common people"—suppliers, contractors, and grey-market intermediaries who operate in the shadows of industry standards.
The dilemma is this: At what point does your "don't ask, don't tell" approach to procurement become an ethical liability? When you source from a marketplace that is a mixture of verified, high-quality sources and unverified, "wild" sources, you are effectively operating in a state of demai—a Talmudic category for produce of uncertain tithing status. Many founders treat their supply chain like wild figs—"If I didn't see the orchard, I'm not responsible for the tax." Rambam, however, argues that your ignorance is not a business strategy; it’s a risk profile. If you don’t know if your inputs are "guarded" (checked) or "ownerless" (raw/unvetted), you are building your product on a shaky foundation of unverified integrity. The question is: Are you building a business that requires external validation, or one that thrives on the assumption of chaos?
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
"Produce that ripens first and last in a valley are exempt from the obligations of demai... Similar produce in a garden is liable, because it is watched." Mishneh Torah, Tithes 13:1
"When a person purchases [produce] from the owners of storehouses in Tyre, he is exempt... We do not say that they stored produce from [the land]... Similarly, if one donkey enters Tyre laden with produce, it is exempt... for we assume that [the produce comes] from the fields around the city." Mishneh Torah, Tithes 13:4
"When there is a majority [of produce from the Diaspora] in a city... those who purchase are permitted. For those where it is not in the majority, they are obligated [to heed the restrictions]." Mishneh Torah, Tithes 13:10
Analysis
Insight 1: The "Garden vs. Valley" Principle of Accountability
Rambam draws a hard line between produce that is "watched" (guarded) and produce that is "ownerless" (wild). In a business context, this is your Audit Trail. When produce grows in a protected garden, the owner is responsible for the tithe. When it grows in a wild valley, it is exempt because there is no system of ownership to regulate it.
The decision rule here is simple: Don’t confuse "unregulated" with "exempt." If you buy from a vendor who has no quality control, you aren't just getting a "good deal"; you are inheriting their lack of process. If you want a high-output, high-integrity product, you must mandate that your supply chain be "watched." If you outsource to a "wild" supplier, you are choosing to accept a lack of data as part of your product’s DNA.
Insight 2: Contextualizing the Source (The "Tyre" Test)
Rambam notes that when produce enters a city like Tyre, we judge its status based on the logistics of the carrier. A single donkey-driver implies local, short-distance sourcing (exempt), while a caravan implies a longer, more complex supply chain (obligated).
The decision rule: The complexity of your supply chain dictates your due diligence requirements. You cannot apply the same governance policy to a local consultant as you do to a global, multi-tier manufacturing partner. As your scale grows—moving from the "single donkey" stage to the "caravan" stage—your assumption of innocence must shift to an assumption of investigation. If you are buying in bulk, the assumption of "clean" inputs vanishes. You have to trace the origin.
Insight 3: The Law of the Majority (Marketplace Dynamics)
Rambam establishes a rule for when you don't know the exact history of a batch: "If produce [from a specific source] constitutes the majority, it is permitted." This is a statistical approach to ethics.
The decision rule: Integrity is a aggregate game. If 80% of your suppliers are verified, you have a baseline of safety. But the moment the "majority" shifts—if your supply chain becomes fragmented—the entire status of your inventory is compromised. You must track your "vendor mix" as a KPI. If your reliance on unverified, "common" suppliers crosses the 50% threshold, your standard operating procedure must immediately flip from "trust" to "verification." You don’t get to pick and choose your ethics; you follow the statistical reality of your marketplace.
Policy Move
Implement the "Provenance Tagging" Policy. Just as the Sages required knowing whether produce came from the "land of the Babylonians" or the "Diaspora," you must mandate that every SKU or service input carries a metadata tag identifying its "Source Category."
- Category A (Guarded): Audited, certified, known provenance. No further action required.
- Category B (Wild/Unverified): Sourced from the "open market" or unvetted contractors. These items must undergo a "Tithing" process—a mandatory secondary check or QA review before they are integrated into your final product.
KPI Proxy: Percentage of Raw Inputs Subject to Secondary Verification (SRV). Aim for this to be inversely proportional to your trust in the supplier. If your "unverified" input percentage rises above 20%, your manual QA costs should automatically trigger a budget review.
Board-Level Question
"If we were forced to undergo a full forensic audit of our supply chain today, which segment of our vendor list would we be unable to defend, and what is the specific cost of replacing that 'wild' source with a 'guarded' one?"
This question forces leadership to quantify the "risk of the unknown." Founders often hide behind the idea that they can’t afford top-tier, transparent suppliers. This question flips the script: Can you afford the cost of the uncertainty in your current, unvetted supply chain?
Takeaway
Integrity isn't just a moral virtue; it's an operational assumption. Whether you are dealing with literal produce or digital code, the "wild" inputs you bring into your system—without checking their origin—eventually define the quality of what you ship. Stop pretending that ignorance is a shield. If you want to build something that lasts, you have to be the one who guards the garden.
derekhlearning.com