Arukh HaShulchan Yomi · Startup Mensch · Standard
Arukh HaShulchan, Orach Chaim 317:28-318:6
Hook
Every early-stage founder faces a structural paradox: you must build things that do not scale while simultaneously preparing your business to survive the pressures of hyper-scale. In the frantic rush to secure market share, you are constantly making structural commitments. You sign multi-year enterprise vendor contracts, allocate equity to early hires, hard-code software architectures, and establish operational processes.
The core dilemma of the early-stage startup is state management: When is a commitment temporary, and when is it permanent?
[ DECISION POINT ]
|
+------------------+------------------+
| |
[ TEMPORARY KNOT ] [ PERMANENT KNOT ]
(Reversible / Agile) (Irreversible / Locked)
| |
Hacks, MVPs, Pilots Equity, Core Architecture,
Enterprise Debt
If you treat a temporary integration as a permanent foundation, you over-engineer your product, burn through precious runway, and miss your market window. Conversely, if you treat a permanent commitment—like a cap table allocation or a core database schema—as a temporary hack, you accumulate catastrophic technical and organizational debt that will tear your company apart when you try to scale.
This is not merely a modern software engineering problem; it is a fundamental challenge of resource preservation and structural design. The laws of Shabbat, specifically as codified by the late 19th-century posek Rabbi Yechiel Michel Epstein in the Arukh HaShulchan Arukh HaShulchan, Orach Chaim 317:28-318:6, offer a remarkably sophisticated framework for managing these exact dynamics.
By analyzing the halachic boundaries of Koshair (tying and untying knots) and Bishul (cooking, or the permanent transformation of substances through energy), the Arukh HaShulchan provides founders with an actionable, highly structured blueprint for decision-making.
This text teaches us how to distinguish between reversible and irreversible decisions, how to manage the "thermal state" of our operational assets, and how to scale execution without losing the vital, founder-driven energy that animates the enterprise. If you want to protect your runway and build a resilient company, you must master the art of the temporary knot and understand the physics of direct vs. indirect organizational heat.
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
אורח חיים שקיז:כח "...כל קשר שאינו עשוי להתקיים לעולם, אלא לעמוד זמן קצר ואחר כך התירו, אין זה קשר של קיימא ומותר להתירו לכתחילה..."
אורח חיים שיח:ד "...כל דבר יבש שנתבשל כל צרכו, אף על פי שנצטנן לגמרי, אין בו משום בישול אם יחזור ויחממנו... דאין בישול אחר בישול בדבר יבש..."
אורח חיים שיח:ה "...אבל בדבר לח, כגון מרק או מים, אם נצטנן לגמרי, יש בו משום בישול אם יחזור ויחממנו... דכל שנצטנן הרי הלך מעשה הבישול הראשון..."
אורח חיים שיח:ב "...כלי ראשון, אפילו לאחר שהעבירוהו מעל האש, מכל מקום כל זמן שהיד סולדת בו – מבשל..."
English Translation
Orach Chaim 317:28 "...Any knot that is not made to endure forever, but rather to stand for a short time and afterwards to be untied, this is not considered a permanent knot, and it is permitted to untie it from the outset..."
Orach Chaim 318:4 "...Any dry item that was fully cooked, even if it has cooled down completely, there is no prohibition of cooking if one goes back and heats it up... for there is no cooking after cooking regarding a dry item..."
Orach Chaim 318:5 "...But regarding a liquid item, such as soup or water, if it has cooled down completely, there is a prohibition of cooking if one goes back and heats it up... for once it has cooled, the effect of the first cooking is gone..."
Orach Chaim 318:2 "...A primary vessel (Kli Rishon), even after it has been removed from atop the fire, nevertheless, as long as it is hot enough to scald the hand (Yad Soledet Bo), it still has the power to cook..."
Analysis
================================================================================
THE THREE OPERATIONAL LAWS
================================================================================
LAW I: REVERSIBILITY LAW II: THERMAL STATE
(Arukh HaShulchan 317:28) (Arukh HaShulchan 318:4-5)
[ Temporary Knot ] [ Dry Asset: Fully Baked ]
• Easily untied. • Retains status when cold.
• Low-cost reversal. • No "re-cooking" needed.
• Use for MVPs & pilots. • Protects runway.
[ Permanent Knot ] [ Liquid Asset: Volatile ]
• High structural cost. • Degrades if heat is lost.
• Irreversible commitment. • Requires continuous energy.
• Require board review. • Culture, Pipelines, CS.
--------------------------------------------------------------------------------
LAW III: THERMAL DELEGATION
(Arukh HaShulchan 318:2-3)
[ Fire Source ] ──> [ Kli Rishon (Primary) ] ──> [ Kli Sheni (Secondary) ]
Founder's Vision Execs & Direct Reports Frontline & Ops
• Retains "cooking" heat. • Cannot cook raw items.
• Can drive change. • Executes stable plays.
================================================================================
Insight 1: The Law of Reversibility (Designing the "Temporary Knot")
In Arukh HaShulchan, Orach Chaim 317:28, Rabbi Yechiel Michel Epstein addresses the complex laws of tying and untying knots on Shabbat. He establishes a clear, binary decision rule: if a knot is not designed to endure permanently ("שאינו עשוי להתקיים לעולם"), but is rather built to serve a short-term purpose and then be undone ("לעמוד זמן קצר ואחר כך התירו"), it does not fall under the biblical prohibition of Koshair (tying). It is fundamentally reversible.
For a startup founder, this is the ultimate halachic validation of the "minimum viable product" (MVP) and the agile methodology. Every decision you make is a knot.
Some knots are permanent: your cap table, your choice of co-founder, your core database architecture, and your regulatory compliance framework. Other knots are temporary: your initial landing page, your manual backend workflows (doing things that don't scale), your temporary contractor agreements, and your early-stage pricing models.
The catastrophic mistake most founders make is misclassifying their knots.
When you treat a temporary knot as a permanent one, you suffer from premature optimization. You spend $100,000 on enterprise-grade security compliance and scalable microservices before you have a single paying customer. You have tied a permanent knot on a structure that you should have kept completely loose.
Conversely, when you treat a permanent knot as a temporary one, you create structural debt. You bring on a co-founder with a handshake agreement and no vesting schedule, thinking, "We’ll tie up the legal loose ends later." You have treated a highly permanent knot as a temporary one, and when that co-founder leaves six months later with 50% of your common stock, your startup is dead.
The Arukh HaShulchan teaches us that the permissibility of an action on Shabbat hinges entirely on the intent of duration. If you design an integration with an explicit expiration date and a clear path to disassembly, it remains a "temporary knot."
In startup operations, every temporary hack must have a built-in "untie" protocol. If you are building a manual workflow to patch a product gap, you must define the exact trigger (e.g., reaching 100 daily active users) that will cause you to untie that manual process and replace it with automated code. Keeping your temporary knots easily untieable preserves your operational agility and protects your runway.
Insight 2: Dry vs. Liquid Deliverables (The Ethics of "Re-cooking" and Scope Creep)
In Arukh HaShulchan, Orach Chaim 318:4 and Arukh HaShulchan, Orach Chaim 318:5, the text introduces a profound physical and conceptual distinction regarding the laws of cooking (Bishul).
The Arukh HaShulchan rules that for a dry item (davar yavesh) that has already been fully cooked, reheating it does not constitute cooking ("אין בישול אחר בישול בדבר יבש"). Once a solid item has reached its mature, cooked state, its physical transformation is complete. Even if it cools down completely, applying heat to it again does not change its fundamental nature; it is merely warming up.
However, for a liquid item (davar lach), such as soup or water, if it cools down completely, reheating it is considered a new act of cooking ("יש בישול אחר בישול בדבר לח") because "once it has cooled, the effect of the first cooking is gone" ("דכל שנצטנן הרי הלך מעשה הבישול הראשון").
This distinction provides founders with a precise framework for categorizing their startup’s operational assets into "Dry" vs. "Liquid" deliverables:
| Asset Class | Halachic Category | Physical Characteristics | Startup Examples | Management Rule |
|---|---|---|---|---|
| Dry Assets | Davar Yavesh (Solid/Dry) | Retains its state once fully cooked. Reheating does not change its essence. | Core APIs, documented playbooks, legal templates, automated billing systems. | Set and Forget. Do not waste capital "re-cooking" fully baked, stable assets. |
| Liquid Assets | Davar Lach (Liquid/Fluid) | Volatile. If heat is removed, it cools completely and requires a full restart. | Customer success pipelines, outbound sales momentum, company culture, brand equity. | Continuous Thermal Maintenance. Requires constant energy to prevent freezing. |
Managing Dry Assets
A "Dry Asset" is a modular, fully baked product feature or operational process. Once you have built a stable, automated billing system that works, it is fully cooked.
The Arukh HaShulchan’s rule of "no cooking after cooking" means that you should not waste valuable engineering hours continuously refactoring or tinkering with this asset. It is stable. It does not require continuous operational energy to maintain its value.
Founders often fall victim to perfectionism, allowing engineers to "re-cook" stable, dry assets under the guise of technical optimization, when that energy should be directed toward raw, unbaked market opportunities.
Managing Liquid Assets
A "Liquid Asset" is highly volatile. It has no structural rigidity.
Consider your customer success pipeline or your outbound sales momentum. If your sales team stops sending outbound emails for three weeks, the pipeline doesn't just sit there waiting for you; it cools down completely. The momentum is lost, and "the effect of the first cooking is gone."
To get that pipeline hot again, you cannot simply flip a switch; you have to expend a massive, capital-intensive amount of energy to "re-cook" it from scratch.
The same applies to company culture. Culture is a liquid asset. It requires continuous, active application of leadership energy. If you stop reinforcing your core values, the culture cools down to room temperature almost instantly, and rebuilding it requires a painful, highly disruptive organizational overhaul.
As a founder, you must audit your operations and identify which assets are dry and which are liquid. You must protect your liquid assets from cooling down, because the capital cost of reheating a liquid asset from a cold state is exponentially higher than the maintenance cost of keeping it warm.
Insight 3: The Physics of Delegation (Kli Rishon vs. Kli Sheni)
How does a founder scale their influence without burning out? The answer lies in the physics of thermal transfer.
In Arukh HaShulchan, Orach Chaim 318:2, the text defines the cooking capacity of different vessels. A Kli Rishon (the primary vessel) is the pot that sat directly on the fire. Even after you remove this vessel from the direct source of heat, as long as it remains hot enough to scald a hand ("כל זמן שהיד סולדת בו"), it still possesses the halachic power to cook raw items.
However, a Kli Sheni (the secondary vessel, into which the contents of the Kli Rishon were poured) generally does not have the power to cook raw food, because its walls are cool and it is disconnected from the original heat source, even if the liquid inside is burning hot.
This thermal gradient is the perfect metaphor for organizational delegation and authority in a scaling startup:
[ THE FOUNDER (THE FIRE) ]
|
v
[ EXECUTIVE LEADERSHIP ]
(Kli Rishon)
• Retains direct heat of the vision.
• Capable of "cooking" raw initiatives.
|
v
[ MIDDLE MANAGEMENT & OPS ]
(Kli Sheni)
• Disconnected from the direct fire.
• Cannot execute highly complex pivots.
• Best suited for standardized playbooks.
- The Fire: The founder's vision, drive, and strategic clarity.
- The Kli Rishon (Primary Vessel): Your executive leadership team (C-Suite, VP level). They are in direct contact with the fire. They absorb the raw vision and strategic intent. Because they are a Kli Rishon, they retain the "heat" of the founder's authority. Even when the founder is not in the room, the Kli Rishon possesses the operational capacity to "cook"—to make hard strategic decisions, execute complex pivots, and transform raw talent into high-performing teams.
- The Kli Sheni (Secondary Vessel): Your middle management, frontline employees, and external contractors. They are one step removed from the original fire. They receive their direction and culture poured out from the Kli Rishon.
The Arukh HaShulchan teaches us a vital organizational lesson here: A Kli Sheni cannot cook raw items.
If you take a highly complex, undefined strategic initiative (raw food) and delegate it directly to a junior engineer or a mid-level manager (a Kli Sheni), it will fail to execute. It will not cook.
The Kli Sheni does not possess the structural heat (the deep context, the strategic authority, the founder's alignment) required to shape raw, ambiguous problems into finished solutions. They will simply freeze, or worse, make decisions that deviate entirely from the company's core mission.
When founders complain, "My team can't execute without me," it is usually because they are pouring raw, uncooked strategic initiatives directly into a Kli Sheni, expecting it to perform like a Kli Rishon.
If you want to execute a complex strategic move, you must either keep it in the Kli Rishon (managed directly by you or your core leadership team) or you must "pre-cook" the initiative—standardizing the processes, documenting the playbooks, and removing the ambiguity—before pouring it down to the Kli Sheni.
Only items that are "easily cooked" (kaleh habishul), meaning highly standardized and routine tasks, can be safely executed in a Kli Sheni.
Policy Move
The "Knot & State Classification Protocol" (KSCP)
To operationalize these insights, your startup must implement a formal Knot & State Classification Protocol (KSCP). This protocol must be integrated into your product management, engineering, and operational workflows.
Before any project is greenlit, any vendor contract is signed, or any new hiring process is initiated, the lead owner must submit a one-page "Thermal & Structural Impact Assessment" classifying the initiative across three halachic-operational dimensions: Knot Permanence, Thermal State, and Vessel Delegation.
================================================================================
KNOT & STATE CLASSIFICATION (KSCP)
================================================================================
[Initiative Name]: ________________________ [Date]: _________________
1. STRUCTURAL KNOT STATUS
[ ] TEMPORARY (Reversible, <30-day exit, Low-cost untie)
- Must include explicit "Untie Trigger": ________________________
[ ] PERMANENT (Irreversible, >12-month lock-in, Cap table impact)
- Requires Board Approval / Co-founder Sign-off
2. THERMAL STATE CLASSIFICATION
[ ] DRY ASSET (Solid/Modular - "Set & Forget" once baked)
[ ] LIQUID ASSET (Volatile - Requires continuous operational heat)
- Monthly Thermal Maintenance Cost (TMO): $____________________
3. VESSEL DELEGATION ASSIGNMENT
[ ] KLI RISHON (Requires direct founder/exec heat to resolve ambiguity)
[ ] KLI SHENI (Fully standardized - can be executed by frontline)
================================================================================
Step-by-Step Implementation
The Knot Classification Rule:
- If an initiative is classified as a Temporary Knot, it must bypass deep architectural reviews and lengthy legal negotiations. You must opt for speed and flexibility. However, the proposal must include an explicit "Untie Trigger" (e.g., "This temporary third-party API integration will be untied and rebuilt in-house once we hit $50k MRR").
- If it is a Permanent Knot (e.g., choosing a cloud provider, allocating equity, signing a lease), it must undergo a rigorous, multi-step review process. It cannot be executed without co-founder sign-off and, if applicable, board-level notification.
The Thermal State Audit:
- Every product feature must be designated as either Dry or Liquid.
- If a feature is Dry (e.g., a static user dashboard), once it passes QA, it is locked. No further engineering hours may be allocated to it for "cosmetic refactoring" without a documented business case showing a clear ROI.
- If a process is Liquid (e.g., your inbound lead nurturing sequence), the team must calculate the Thermal Maintenance Overhead (TMO). This is the weekly human and financial capital required to keep this asset from "cooling down" to zero. If the TMO is too high for your current runway, you must either automate it (converting it into a dry asset) or kill the initiative entirely.
The Delegation Routing Engine:
- Before assigning a task, the project leader must ask: "Is this task raw (ambiguous, requiring strategic judgment) or cooked (standardized, playbook-driven)?"
- Raw tasks must be routed exclusively to a Kli Rishon (the founder or their direct reports who hold the core strategic context).
- Cooked tasks are routed to the Kli Sheni (external contractors, junior employees, or automated workflows). If a raw task must be delegated to a Kli Sheni, it must first go through a "Pre-Cooking Phase" where a Kli Rishon writes a step-by-step playbook, converting the raw strategic ambiguity into a highly structured, repeatable process.
Key Metric: The Thermal Maintenance Ratio (TMR)
To measure the operational efficiency of your startup under this protocol, you will track your Thermal Maintenance Ratio (TMR) on a monthly basis:
$$\text{TMR} = \frac{\text{Total Capital & Labor Spent on Reheating Liquid Assets}}{\text{Total Capital & Labor Spent on Cooking New Value}}$$
Where:
- Reheating Liquid Assets includes: Re-engaging cold sales pipelines, rebuilding broken team cultures, manual operational work to patch unautomated product gaps, and refactoring stable "dry" codebase features.
- Cooking New Value includes: Developing new product features, acquiring new customers, and hiring strategic talent.
[ HIGH TMR (Danger) ] [ LOW TMR (Healthy) ]
┌─────────────────────────────┐ ┌─────────────────────────────┐
│ Reheating Cold Assets: 70% │ │ Reheating Cold Assets: 20% │
│ │ │ │
│ Cooking New Value: 30% │ │ Cooking New Value: 80% │
└─────────────────────────────┘ └─────────────────────────────┘
Runway wasted on maintenance. Runway focused on growth.
Target Metric: Your TMR should remain below 0.25. If your TMR exceeds 0.25, it means more than 25% of your company's monthly burn is being wasted on "reheating" cold assets and re-cooking dry deliverables. This is a clear indicator of structural inefficiency, premature optimization, or poor delegation. It signals to leadership that the company is burning runway just to stand still.
Board-Level Question
"Are we spending our limited runway on re-cooking dry assets while letting our liquid assets freeze, and are we delegating raw initiatives to vessels that lack the thermal capacity to execute them?"
Context and Strategic Implications
As a board member or founder, you must look beyond high-level financial metrics like burn rate and CAC/LTV. You must analyze the operational physics of how capital is being converted into enterprise value.
When a startup presents a high burn rate with flat growth, the immediate reaction is often to cut head count or increase marketing spend. However, the root cause is frequently a violation of the thermal laws outlined by the Arukh HaShulchan.
================================================================================
BOARD AUDIT FRAMEWORK (KSCP)
================================================================================
[ QUESTIONS FOR THE BOARD TO ASK THE EXECUTIVE TEAM ]
1. THE DRY/LIQUID AUDIT
"Can we review our engineering roadmap to ensure we aren't spending
valuable sprints 're-cooking' stable, dry assets (e.g., rebuilding
internal admin tools) instead of shipping raw, market-facing features?"
2. THE THERMAL DEGRADATION AUDIT
"Which of our core customer acquisition channels are 'liquid' assets?
Are we protecting their thermal state, or are we allowing them to cool
completely every time we divert our attention to a new shiny object?"
3. THE DELEGATION EFFICIENCY AUDIT
"Are our key strategic initiatives stalling because we have delegated
raw, highly ambiguous outcomes (Kli Rishon tasks) directly to junior
teams or external agencies (Kli Sheni) without direct leadership heat?"
================================================================================
If your executive team is spending 40% of their engineering cycles refactoring a database that is already "fully cooked" and serving its purpose, they are violating the rule of Ein bishul achar bishul (no cooking after cooking). They are wasting capital on dry assets that do not require reheating, while their core sales pipeline (a highly liquid asset) is cooling down to absolute zero because no one is feeding the fire.
Furthermore, if your strategic initiatives are stalling, it is rarely a talent problem; it is a structural delegation problem. If the board sees that a critical product pivot or a new market entry is failing to launch, you must ask whether the initiative has been poured into a Kli Sheni (e.g., outsourced to a development agency or handed off to a junior product manager) without the direct, scald-level heat (Yad Soledet Bo) of a Kli Rishon (a co-founder or a highly aligned VP).
By forcing the executive team to present their operations through this structural and thermal lens, the board can identify exactly where capital is being misallocated, protect the company's runway, and ensure that the founder's original fire is being efficiently directed to the areas of highest leverage.
Takeaway
The Arukh HaShulchan teaches us that sustainable creation requires a precise mastery of state, duration, and energy transfer.
Do not paralyze your startup by tying permanent knots on temporary structures, and do not destroy your equity by treating permanent commitments as temporary hacks Arukh HaShulchan, Orach Chaim 317:28.
Protect your runway by locking in your fully baked "dry" assets and focusing your scarce energy on keeping your volatile "liquid" assets warm Arukh HaShulchan, Orach Chaim 318:4-5.
Finally, never forget that you cannot delegate raw strategic ambiguity to teams that lack the direct, thermal context of your vision Arukh HaShulchan, Orach Chaim 318:2. Keep raw initiatives close to the fire, standardise them before you delegate, and build a structure that scales without losing its heat.
derekhlearning.com