Daily Mishnah · Startup Mensch · Standard
Mishnah Kelim 17:8-9
Hook
As a founder, you are constantly lied to by your own metrics. You look at your dashboard and see "active users," but deep down, you know those users are just wandering through a broken workflow, unable to extract real value. You look at your gross margins and see a healthy 75%, yet your bank account is draining because hidden operational overhead is absorbing your cash like a sponge. You sign Service Level Agreements (SLAs) with enterprise clients that your engineering team can only hit by running on a perpetual treadmill of burnout, praying that a single server outage doesn't trigger a catastrophic clawback.
The core dilemma of the scale-up phase is the illusion of functional integrity. We build systems, products, and contracts, and we assume that because they are technically "functional" on paper, they are ethically and operationally sound. But true operational health is not binary. It exists in the messy gray area between absolute failure and optimal utility.
When is a product truly dead? When is a contract structurally dishonest? How do we build systems that protect us from our own inevitable human errors without sacrificing our margins?
The answers are not found in modern, venture-backed growth hacks. They are coded into the ancient, hyper-granular laws of ritual purity in Mishnah Kelim 17:8-9. This text is not a dry theological exercise; it is an incredibly sophisticated manual on operational utility, structural margins, and the ethics of measurement. It addresses the exact moment a tool ceases to be a tool, how to design systems that prevent accidental ethical breaches, and how to measure the true, unabsorbed value of your assets.
If you are tired of vanity metrics and want to build a business that is structurally honest, highly profitable, and resilient under pressure, you need to stop looking at your spreadsheet and start looking at the Shushan gate.
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
"...But why were there a larger and a smaller cubit? Only for this reason: so that craftsmen might take their orders according to the smaller cubit and return their finished work according to the larger cubit, so that they might not be guilty of any possible trespassing of Temple property..." — Mishnah Kelim 17:9
"...The olive of which they spoke it is one that is neither big nor small but of moderate size the egori." — Mishnah Kelim 17:8
"...זה אגורי . ל' הר"ב ששמנו אגור בתוכו... שאינו נבלע בפרי כמשקה תפוחים ותותים. אלא אגור כמשקה ענבים:" — Tosafot Yom Tov on Mishnah Kelim 17:8:1
Analysis
Insight 1: The SLA of Broken Things (Contextual vs. Standardized Utility)
In Mishnah Kelim 17:8, the Sages debate a fundamental question: when does a broken vessel lose its status as a "vessel"? In the laws of purity, a broken vessel that can no longer perform its function becomes "clean" (pure) because it is no longer considered a functional object. But how do we define "broken"?
The Mishnah presents a classic clash of product philosophies:
"All [wooden] vessels that belong to householder [become clean if the holes in them are] the size of pomegranates. Rabbi Eliezer says: [the size of the hole depends] on what it is used for."
Rabbi Joshua argues for a standardized, flat metric: if a hole is the size of a pomegranate, the vessel is dead, regardless of what it holds. Rabbi Eliezer, the ultimate product-market fit pragmatist, disagrees. He argues that utility is hyper-contextual:
"Gardeners’ vegetable baskets [become clean if the holes in them are] the size of bundles of vegetables. Baskets of householders... the size of [bundles] of straws. Those of bath-keepers, if bundles of chaff [will drop through]."
In the startup world, we are constantly tempted by Rabbi Joshua’s approach. We want clean, standardized KPIs. We define "churn" or "product adoption" using uniform metrics across our entire customer base. But Rabbi Eliezer’s view is the reality of operations: a product's utility is defined solely by its specific use-case and user persona. If you run a B2B SaaS platform, a 2-second latency might be completely acceptable (a "pomegranate-sized hole") for a backyard gardener tracking inventory, but it is a fatal, contract-killing breach (a "chaff-sized hole") for an enterprise bath-keeper running real-time financial transactions.
The Mishnah takes this contextual analysis even deeper:
"A dish holder that cannot hold dishes but can still hold trays remains unclean. A chamber- pot that cannot hold liquids but can still hold excrements remains unclean. Rabban Gamaliel rules that it is clean since people do not usually keep one that is in such a condition."
This is a masterclass in product sunsetting and technical debt. If a dish holder can no longer hold its primary object (dishes) but can still hold a secondary object (trays), it is still legally a "vessel." It still has residual utility. In startup terms, this is the pivot. Your primary feature is broken, but your customers are hacking your platform to do something else.
However, Rabban Gamaliel introduces a critical ethical and operational boundary with the chamber-pot: if a product is so degraded that its only remaining utility is highly specialized and socially undesirable, it must be declared dead ("clean").
Do not keep zombie products alive just because they have a tiny sliver of residual utility. If your legacy software requires manual, high-friction intervention from your engineering team to keep one low-paying customer happy, you are keeping a broken chamber-pot in your living room. It is time to sunset the feature, declare it "clean," and redeploy your resources.
[Standardized Metric (Rabbi Joshua)]
│
Does it have a hole?
┌───────┴───────┐
YES NO
│ │
[Declared Dead] [Functional]
VS.
[Contextual Utility (Rabbi Eliezer)]
│
What is the specific use-case?
┌────────────┼────────────┐
(Gardeners) (Householders) (Bath-keepers)
│ │ │
[Vegetable [Straw [Chaff
Bundles] Bundles] Bundles]
Insight 2: The Double-Cubit Principle (Designing Systemic Ethical Margins)
The most profound operational insight in this text lies in the architectural design of the ancient Temple in Jerusalem. Mishnah Kelim 17:9 describes two standard cubits (physical measuring rods) kept in the palace of Shushan Habirah:
"There were two standard cubits in Shushan Habirah, one in the north-eastern corner and the other in the south-eastern corner. The one in the north-eastern corner exceeded that of Moses by half a fingerbreadth, while the one in the south-eastern corner exceeded the other by half a fingerbreadth..."
Why did the Temple administration maintain two different physical standards of measurement, both of which were larger than the actual biblical standard (the cubit of Moses)? The Mishnah explains:
"...so that craftsmen might take their orders according to the smaller cubit and return their finished work according to the larger cubit, so that they might not be guilty of any possible trespassing of Temple property."
This is a masterclass in systemic risk mitigation. The Sages did not rely on the moral perfection of the craftsmen. They did not say, "Just try your hardest not to accidentally steal Temple materials." Instead, they designed a physical, structural buffer into the measurement system itself.
The craftsman took raw materials and specifications based on the smaller cubit, but when he delivered the finished gate, pillar, or vessel, it was measured against the larger cubit. The craftsman had to deliver more physical material than he was technically paid for, entirely at his own expense, to absorb any human error, tool wear, or material shrinkage.
This is the exact opposite of how modern startups negotiate. Founders, desperate to win enterprise contracts, do the reverse: they sell according to the "larger cubit" (promising 99.99% uptime, instant support, and bespoke feature delivery) but build according to the "smaller cubit" (using an understaffed engineering team and unstable infrastructure). They operate with zero buffer, meaning any slight operational hiccup results in me'ilah—an ethical and legal trespass of the client’s trust and contract.
The Double-Cubit Principle demands that you build a structural asymmetry into your commitments. If your system can comfortably deliver a 1-second response time, your public SLA must be 2 seconds. If your engineering team estimates a feature will take 4 weeks, you promise it to the client in 6 weeks.
You "take your orders" (set expectations) by the smaller measure, and "return your finished work" (deliver) by the larger measure. This is not deception; it is systemic humility. It is an explicit acknowledgment that you are human, your code has bugs, your supply chain has delays, and the only way to guarantee you never "trespass" on your customer's trust is to pay for a protective buffer out of your own margin.
Insight 3: The "Egori" Metric (Capital Efficiency and Value Retention)
When the Mishnah establishes the standard units of measurement for ritual purity, it repeatedly insists on using "moderate" sizes—neither too large nor too small. But when it defines the standard "olive" (kezayit), which is the baseline metric for almost all biblical volumes, it specifies a highly particular variety:
"The olive of which they spoke it is one that is neither big nor small but of moderate size the egori." — Mishnah Kelim 17:8
Why the egori olive? The Rash MiShantz and the Tosafot Yom Tov, drawing on the Talmud Berakhot 39a, provide a fascinating botanical and linguistic analysis:
"Why is it called egori? Because its oil is gathered (agur) inside it." — Rash MiShantz on Mishnah Kelim 17:8:2
The Tosafot Yom Tov adds a critical distinction:
"...its oil is gathered inside it... it is not absorbed into the fruit like the juice of apples and mulberries, but rather gathered like the juice of grapes." — Tosafot Yom Tov on Mishnah Kelim 17:8:1
This is an incredibly powerful metaphor for unit economics and capital efficiency.
In business, your revenue is the "juice" of the fruit. Some startups are like apples or mulberries: they look massive, juicy, and impressive from the outside. But when you press them, the juice is deeply absorbed into the pulp. The cost of goods sold (COGS), customer acquisition costs (CAC), and operational friction are so tightly bound to the revenue that you cannot extract the profit without destroying the fruit. The value is dissipated throughout the complex, high-friction operational structure of the company.
An egori startup is different. Its value is "gathered inside it." The gross margin is highly liquid, clean, and easily extracted because it is not absorbed by operational overhead.
[Apple/Mulberry Revenue Model] [Egori Olive Revenue Model]
┌────────────────────────────┐ ┌───────────────────────────┐
│ Revenue & Cost Combined │ │ ┌─────────────────────┐ │
│ (Juice absorbed in pulp) │ │ │ Gathered Oil │ │
│ │ │ │ (Liquid, Extract- │ │
│ Operational friction, │ │ │ able Gross Margin) │ │
│ high CAC, and heavy COGS │ │ └─────────────────────┘ │
│ are bound to the asset. │ │ Minimal pulp/friction. │
└────────────────────────────┘ └───────────────────────────┘
When you evaluate your product lines, marketing channels, or business units, you must ask: are we measuring our success by the total volume of the fruit (top-line revenue), or by the egori standard?
If you add $1M in ARR, but it requires hiring four new customer success managers and two solutions engineers to keep those clients from churning, that revenue is "absorbed like apple juice." It is highly impure from an efficiency standpoint.
You must relentlessly optimize for egori revenue—revenue where the profit margin is structured as a distinct, unabsorbed layer that can be easily gathered and reinvested.
Policy Move
The Dual-Cubit SLA and Resource Protocol
To operationalize the Double-Cubit Principle, your company will implement a Dual-Cubit SLA and Resource Protocol. This policy eliminates "ethical trespassing" (accidental breach of client trust, contract violations, and team burnout) by hardcoding a structural delta between your internal engineering targets and your external client commitments.
THE DUAL-CUBIT SLA FRAMEWORK
[Moses Cubit] ────► [Smaller Cubit] ───────────────► [Larger Cubit]
Absolute Tech External SLA Internal Target
Capability (Contractual Promise) (Engineering Spec)
e.g., 500ms e.g., 2000ms e.g., 1000ms
Raw system limit "Take the order" "Return the work"
┌────────────────────────────────┐
│ Ethical Safety Buffer (50%) │
│ Paid by company's margin │
└────────────────────────────────┘
1. Contractual Standard ("The Smaller Cubit")
All outbound sales contracts, marketing materials, and public Service Level Agreements (SLAs) must be drafted using "the smaller cubit."
- This represents a highly conservative, easily achievable standard of performance.
- If your engineering team proves that the system can consistently achieve a 1-second response time under peak load, your contractual SLA is set to 2 seconds (a 100% safety buffer).
- If your product roadmap indicates a feature will be stable in Q3, the client-facing launch date is locked for Q4.
2. Engineering and Operational Target ("The Larger Cubit")
The internal product requirements document (PRD), engineering sprints, and DevOps monitoring alerts must be set to "the larger cubit."
- The engineering team is budgeted, resourced, and evaluated based on hitting the larger standard (e.g., maintaining a 1-second response time).
- If internal performance slips to 1.5 seconds, it is treated as a Severity 1 incident, even though the external customer is experiencing absolutely zero breach of the 2-second contractual SLA.
3. The "Trespass" Buffer Budget
The cost of maintaining this buffer (e.g., excess server capacity, redundant inventory, or additional support staff) is explicitly categorized on your P&L as the Ethical Safety Buffer (ESB).
- This is not viewed as wasted capital; it is the insurance premium paid to guarantee brand integrity and prevent me'ilah (trespassing on customer trust).
- The ESB is capped at a maximum of 5% of total operational cost, ensuring the buffer remains economically viable while maintaining structural integrity.
KPI Proxy: The Shushan Variance Index (SVI)
To measure the health of your operational buffers, you will track the Shushan Variance Index (SVI) weekly.
$$\text{SVI} = \frac{\text{Actual Internal Performance} - \text{Contractual SLA Promise}}{\text{Contractual SLA Promise}}$$
- SVI < -0.30 (Healthy Buffer): You are operating in the "Shushan Zone." Your internal performance is at least 30% better than your external promises. You have ample structural margin to absorb unexpected spikes, employee sick leave, or technical debt without breaching client trust.
- SVI between -0.30 and 0.00 (Danger Zone): Your buffer is eroding. You are meeting your contracts, but your team is running hot. Any minor systemic failure will result in an ethical and contractual breach.
- SVI > 0.00 (Ethical Trespass): You are in active breach. You are taking orders by the larger cubit and delivering by the smaller cubit. Immediate operational freeze is required to re-align resources.
Board-Level Question
"Are we running an 'Egori' business, or is our gross margin being silently absorbed by operational complexity?"
To open this strategic discussion with your leadership team and board of directors, present them with the following diagnostic framework based on Mishnah Kelim 17:8 and its commentaries:
MARGIN ABSORPTION AUDIT
Is your revenue like Apple Juice or Egori Olive Oil?
[APPLE JUICE] [EGORI OLIVE]
High-friction, absorbed revenue. High-efficiency, clean revenue.
Does scaling this product line Can we grow this revenue stream
require a linear increase in without a corresponding linear
headcount, manual onboarding, increase in support, account
or bespoke engineering? management, or COGS?
┌─────────┴─────────┐ ┌─────────┴─────────┐
YES NO YES NO
│ │ │ │
[High Absorption] [Investigate] [Egori Revenue] [Investigate]
The Context for the Board
"In Mishnah Kelim 17:8, the Sages define the standard of measurement using the egori olive because, as the Tosafot Yom Tov explains, its oil is 'gathered inside it' and 'not absorbed into the fruit like the juice of apples and mulberries' Tosafot Yom Tov on Mishnah Kelim 17:8:1.
When we look at our current revenue growth, we must ask ourselves: is our margin highly liquid and 'gathered' like the egori olive, or is it structurally bound to and absorbed by our operational complexity like apple juice?
If our top-line revenue is growing at 40% year-over-year, but our customer success, solutions engineering, and cloud hosting costs are growing at 38%, we are not building a scalable business. We are building an apple-juice business where the pulp of operational friction is soaking up all our liquidity. We need to identify which of our customer segments, product features, and distribution channels are true egori assets—where the gross margin can be cleanly extracted and reinvested without scaling our headcount linearly."
Direct Questions for the Board and Executive Team
- Identify the "Chamber-Pots": Which of our legacy products or customer accounts are currently operating like the broken chamber-pot in Mishnah Kelim 17:8—retaining only a highly specialized, high-friction utility that we are keeping alive solely to avoid a short-term dip in vanity ARR?
- Quantify the Operational Pulp: If we were to freeze all hiring today, which of our revenue streams would immediately stall or collapse because the "juice" of their value is too deeply absorbed by the manual labor of our team?
- Audit the Shushan Gate: Are we currently setting our sales targets and pricing models using the "larger cubit" of our absolute best-case capacity, thereby guaranteeing that any standard human error or system latency results in an ethical trespass (me'ilah) against our clients Mishnah Kelim 17:9?
Takeaway
True business ethics is not about writing a vague code of conduct or donating a percentage of your profits to charity. It is about the structural integrity of your everyday operations.
As Mishnah Kelim 17:8-9 teaches us, safety, honesty, and efficiency must be physically designed into the tools and metrics of your enterprise.
Do not commit your business to arbitrary, standardized benchmarks when your operational reality is deeply contextual. Build physical, measurable buffers—the double cubits of Shushan—into your SLAs and product roadmaps so that your inevitable human errors never turn into ethical breaches. And ruthlessly audit your revenue streams to ensure you are building an egori business, where your profit is clean, liquid, and gathered, rather than absorbed by the compounding friction of your own growth.
Be a mensch. Build with margin. Measure with truth.
derekhlearning.com