Daily Rambam Accelerated · Startup Mensch · On-Ramp
Mishneh Torah, Tithes 10-12
Hook
As a founder, you live in the "trust gap." You are constantly asking: Who can I trust with my IP? Who is actually doing the work they claim? Who is cutting corners while I’m in the boardroom? The startup world often incentivizes the "common person" (am ha'aretz) approach—the "move fast and break things" mentality where the outcome matters more than the integrity of the process. But Rambam’s Mishneh Torah, Tithes 10-12 Mishneh Torah, Tithes 10 presents a radical alternative: the Chavair (the "friend" or "trustworthy partner").
The dilemma is simple: do you build a company where you have to audit every single output, or do you build a culture of "trustworthy agents"? When we ignore the integrity of our supply chains—whether those are code repositories, HR policies, or client deliverables—we inevitably find ourselves managing "tithes" (the remnants of incomplete work) that poison the product. Today, on Rosh Chodesh Tamuz, we enter a month often associated with reflection on boundaries and the potential for tragic fractures (as we approach the Three Weeks). The text forces a hard question: Is your organization a collection of transactional actors, or is it a Chavair-network where the process is so rigorous that the word of your team is as good as a signature?
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
"When a person makes a commitment to be considered trustworthy with regard to the tithes... he must tithe that which he eats, that which he sells, and that which he purchases... Every Torah scholar is always considered trustworthy. There is no necessity to investigate his conduct." Mishneh Torah, Tithes 10:1
"If a person was considered trustworthy, but his wife was not... we may purchase produce from him, but we do not accept his hospitality." Mishneh Torah, Tithes 10:8
"When a common person gives a meah to a chavair and tells him: 'Buy me a bunch of vegetables,' he may purchase it for him without any qualification... If [the agent] exchanged the meah, he is obligated to tithe." Mishneh Torah, Tithes 10:14
Analysis
Insight 1: The Principle of "Institutionalized Reliability"
The text defines the Chavair not by their title, but by their commitment to a public standard. Rambam notes that the Chavair makes these commitments "in public" Mishneh Torah, Tithes 10:1. In a startup, this is your SOP (Standard Operating Procedure). A Chavair culture is one where the standard is not a secret, and it is not negotiable. When an employee acts as your agent—buying vegetables, or in our case, procuring software or hiring contractors—they are bound by the standards they have publicly committed to. If they deviate, they lose their status as a "trustworthy agent."
Decision Rule: Do not rely on private "hopes" for quality control. You must establish a "public commitment" layer. If your team cannot perform their duties with the same standard when you are not looking as when you are, they are not Chavairim; they are transactional agents. You should only delegate to those who have "publicly" (via clear, documented, and agreed-upon KPIs) accepted the standard of the firm.
Insight 2: The "Split-Domain" Risk
Rambam offers a chilling insight: "If his wife is trustworthy and he is not, we may accept his hospitality, but we do not purchase produce from him" Mishneh Torah, Tithes 10:8. This is a masterclass in risk segmentation. In business, we often treat the whole entity as "good" or "bad." Rambam teaches that trust is context-specific. You may trust your CTO with product architecture but recognize they are a disaster with financial reporting.
Decision Rule: Never delegate across domains without checking the integrity of that specific domain. If your head of sales is "untrustworthy" regarding data entry (the "produce"), you can keep them on the team (hospitality), but you must stop them from managing the CRM (purchasing). Segmentation isn't a lack of loyalty; it’s an ethical requirement to prevent the spread of "untithed" (unverified) data.
Insight 3: The "Agent’s Burden" in High-Growth
When an agent purchases on behalf of a common person, the obligation to tithe shifts based on the visibility of the transaction. If the agent makes their agency explicit—stating they are buying for another—the seller is put on notice Mishneh Torah, Tithes 10:14. The insight here is about transparency of intent.
Decision Rule: Your team must be required to identify the "client" or the "ultimate purpose" of every procurement or task. If they hide the intent, the quality of the work is compromised. The Chavair who is honest about who they are buying for forces the system to maintain its integrity. If your employees hide the end-user or the real goal of a project, the internal "tithes" (checks and balances) are bypassed, and the entire "batch" of work becomes suspect.
KPI Proxy: The "Audit-to-Trust Ratio." Divide the number of hours spent auditing your team's output by the number of hours spent on productive output. A high ratio indicates your team is "common" (untrustworthy); a low ratio indicates you have successfully cultivated a Chavair culture where you can rely on their word.
Policy Move
The "Public Commitment" Audit: Move away from nebulous "culture fit" and implement a "Commitment to Standards" process. Every quarter, key leads must sign a "Trust Affidavit" for their specific domain, explicitly acknowledging the standards they are responsible for upholding (e.g., "I, the Head of Engineering, verify that all external code commits meet X, Y, and Z security standards"). This isn't just paperwork; it mirrors the requirement that a Chavair makes their commitment "in public" Mishneh Torah, Tithes 10:1.
This policy changes the burden of proof. Instead of you spending your time auditing them, the burden is on them to demonstrate that they have met the public standard they committed to. If they fail, they are treated as an am ha'aretz in that domain—their word is no longer accepted, and they are subject to mandatory, manual review until they regain their standing.
Board-Level Question
"Looking at our current operational dependencies, which of our internal 'suppliers' (employees or departments) are currently operating under the assumption that we trust their word, even though they have never publicly committed to the standards we expect, and where is that 'untithed' (unverified) work causing us to incur hidden, systemic risk?"
Takeaway
Rosh Chodesh Tamuz reminds us that we are entering a time where we must be vigilant about the boundaries of our community. A Chavair isn't someone who is perfect; they are someone who is predictable because they have aligned their private actions with a public standard. Build a company of Chavairim, or you will spend your entire career playing the role of the auditor, forever verifying the "tithes" of people you shouldn't have to watch in the first place. Stop managing the people; start enforcing the standard.
derekhlearning.com