Arukh HaShulchan, Orach Chaim 318:32-40

Hook

Every venture-backed founder eventually learns the dangerous art of the "buffer layer."

When you are a seed-stage startup, you do everything yourself. You are the primary heat source. You write the code, you make the sales calls, and you face the immediate consequences of your actions. If you burn something, your hand is directly on the stove.

But as you scale to Series A, B, and beyond, your operation undergoes a thermodynamic shift. You begin to build buffers. You hire an outsourced lead-generation agency to run high-volume cold outreach. You contract a third-party content farm to handle SEO. You deploy automated algorithmic pricing models. You set up offshore customer support teams to handle high-friction user complaints.

When you do this, you tell yourself a comforting lie: “I am no longer cooking. I have moved the heat to a secondary vessel. If the agency spams people, if the algorithm colludes, or if the offshore team mistreats customers, that’s on them. We are insulated.”

This is the classic ethical delusion of the Kli Sheni (the secondary vessel). You believe that because you are one step removed from the direct fire of execution, you are absolved of the consequences of the heat. You think distance equals safety.

It does not.

In the laws of Shabbat, the transition of heat from a primary vessel (Kli Rishon) to a secondary vessel (Kli Sheni) is one of the most sophisticated thermodynamic frameworks ever written. It is a study in how energy, influence, and responsibility dissipate—or fail to dissipate—as they move away from the source.

The Arukh HaShulchan demonstrates that distance does not automatically grant immunity. If the heat is still high enough to scald (Yad Soledet Bo), and if the material you are exposing to that heat is delicate (Kaleh HaBishul), you are still cooking. You are still transforming the state of the system, and you are still liable.

If you are using intermediaries, automated systems, or outsourced partners to do the high-risk work you are too polite to do yourself, you aren't insulating your business. You are simply hiding the fire while keeping the heat. Let's look at how the mechanics of halachic thermodynamics can save your company from a catastrophic, downstream ethical meltdown.

---

Text Snapshot

הלכות בישול, ערוך השולחן, אורח חיים שיח:לב-מ "כלי שני אינו מבשל... מכל מקום יש דברים שהם קלי הבישול, שמתבשלים אפילו בכלי שני... ואצלו כלל גדול: כל שהיד סולדת בו, יש לחוש בו משום בישול אם הוא מקלי הבישול. ובדבר גוש, אפילו בכלי שני דינו ככלי ראשון, שהרי אינו מתקרר מדפנות הכלי..."

Arukh HaShulchan, Orach Chaim 318:32, 39 "A secondary vessel (Kli Sheni) does not generally cook... nevertheless, there are items that are easily cooked (Kaleh HaBishul), which cook even in a secondary vessel... And we have a great principle: as long as the hand recoils from its heat (Yad Soledet Bo), we must worry about cooking if it is of the easily cooked items. And regarding a solid mass (Davar Gush), even in a secondary vessel its status is like a primary vessel, because it does not cool down from the walls of the vessel..."

---

Analysis

To build an enduring enterprise, you must master the thermodynamics of organizational influence. The Arukh HaShulchan provides a masterclass in how energy transfers through systems, laying down three precise decision rules for founders who manage delegated authority, algorithmic systems, and external partnerships.

[Primary Heat Source: Founder/HQ] (Kli Rishon)
       │
       ▼  (Direct Heat Transfer / High Energy)
[Secondary Partner/System] (Kli Sheni)
       │
       ├─► [Vulnerable Market/Data] (Kaleh HaBishul) ──► *CRITICAL VIOLATION* (State Change/Damage)
       │
       └─► [Solid Legacy Asset/Executive] (Davar Gush) ──► *RETAINS KLI RISHON HEAT* (High Risk)

Insight 1: The Illusion of the Secondary Vessel (The Thermodynamics of Delegation)

The fundamental rule of Shabbat cooking is that cooking can only occur in a vessel that has sat directly on the fire (Kli Rishon). When you pour that hot liquid into a second vessel (Kli Sheni), the Halacha generally rules that the Kli Sheni does not cook:

"כלי שני אינו מבשל" "A secondary vessel does not cook" Arukh HaShulchan, Orach Chaim 318:32

Why? Because the physical properties of a Kli Sheni are different. The walls of the secondary vessel are cold. When you pour hot water into a cold bowl, the bowl immediately begins to absorb and dissipate the heat. The energy state is in decline.

In business, founders treat their vendors, agencies, and automated systems as Kli Sheni. You draft a Master Services Agreement (MSA) with an outsourced sales agency. The MSA has indemnification clauses. It has compliance checkmarks. You tell yourself, “The fire of the sales push is in their office, not mine. If they use misleading tactics, they are the ones on the fire. We are just receiving the leads in our cold CRM (our Kli Sheni).”

But the Arukh HaShulchan immediately complicates this easy assumption:

"מכל מקום יש דברים שהם קלי הבישול, שמתבשלים אפילו בכלי שני" "Nevertheless, there are items that are easily cooked, which cook even in a secondary vessel" Arukh HaShulchan, Orach Chaim 318:32

The halachic reality is that distance does not guarantee safety if the medium you are acting upon is highly sensitive. If the liquid in your secondary vessel is still hot enough to burn a hand—a temperature defined as Yad Soledet Bo (typically 110°F to 120°F)—and you drop an easily cooked item (Kaleh HaBishul) into it, you have violated the laws of Shabbat.

Translate this to your business: Your ethical liability is not determined by the number of organizational layers between you and the action; it is determined by the residual energy of your instructions and the vulnerability of the target.

If you set an aggressive, near-impossible sales target for your outsourced agency (maintaining the heat at Yad Soledet Bo), and they target low-income, financially illiterate consumers to hit that target (an easily cooked medium, Kaleh HaBishul), you cannot claim insulation. The pressure you exerted at the source (Kli Rishon) carried over to the secondary vessel (Kli Sheni), and because the market segment was highly vulnerable, a state change (damage/exploitation) occurred.

The decision rule is clear: You cannot use delegation to lower your ethical standards if the residual pressure of your incentives remains high enough to exploit vulnerable stakeholders.

Insight 2: The Vulnerability Metric (Identifying Your "Kaleh HaBishul")

How do we determine what constitutes an "easily cooked" item in a business ecosystem? The Arukh HaShulchan notes that we do not have an exhaustive, explicit list of every item that is Kaleh HaBishul:

"ואצלו כלל גדול: כל שהיד סולדת בו, יש לחוש בו משום בישול אם הוא מקלי הבישול" "And we have a great principle: as long as the hand recoils from its heat, we must worry about cooking if it is of the easily cooked items" Arukh HaShulchan, Orach Chaim 318:32

Because we cannot always identify every sensitive item with absolute certainty, we must err on the side of caution whenever high heat is present.

In startup operations, your Kaleh HaBishul represents any asset, stakeholder, or regulatory boundary that cannot withstand indirect pressure without undergoing a damaging state change. Examples include:

1. User Trust and Privacy: A database of user emails is Kaleh HaBishul. If your marketing partner runs an "indirect" campaign using gray-hat scraping tools, that database will be "cooked" (blacklisted, marked as spam, or hit with a GDPR fine) almost instantly, even if you didn't run the script yourself.
2. Early-Stage Culture: Your first ten employees are Kaleh HaBishul. If you hire a brilliant but toxic VP of Sales (Kli Rishon) and let them manage the team (Kli Sheni), the culture will turn toxic immediately. The fragile alignment of an early team cannot withstand the indirect heat of a toxic executive.
3. Regulatory Goodwill: If you operate in a highly regulated space (Fintech, Healthtech, Insurtech), your relationship with regulators is incredibly delicate. If your growth team deploys "clever" copy that skirts the edges of compliance, the regulator will react with the speed of an egg hitting boiling water.

The Arukh HaShulchan teaches us that we cannot treat all materials equally. You might be able to put a hard, pre-cooked piece of meat (Davar Gush) into a secondary vessel without consequence, but you cannot do the same with a raw egg.

As a founder, you must map your dependencies. If you are throwing high-energy incentives or aggressive growth tactics into your ecosystem, you must know exactly which parts of your business are raw eggs and which are cured meat. If your growth tactics are hot enough that your compliance officer's hand recoils (Yad Soledet Bo), you must keep those tactics far away from your vulnerable assets.

Insight 3: The Untamed Variable (The "Davar Gush" Exception)

Perhaps the most profound thermodynamic concept in the Arukh HaShulchan is the law of the Davar Gush (a solid, dense mass):

"ובדבר גוש, אפילו בכלי שני דינו ככלי ראשון, שהרי אינו מתקרר מדפנות הכלי" "And regarding a solid mass, even in a secondary vessel its status is like a primary vessel, because it does not cool down from the walls of the vessel" Arukh HaShulchan, Orach Chaim 318:39

This is an extraordinary physical and ethical insight. If you take a hot potato or a dense piece of meat out of the primary pot (Kli Rishon) and place it into a secondary plate (Kli Sheni), that solid item retains its status as a primary vessel. It does not cool down. Why? Because unlike a liquid, which immediately touches the cold walls of the secondary vessel and dissipates its heat, a dense solid traps its heat inside its core. It remains a roving source of intense, direct energy. If you pour oil or spices onto that hot potato, they will cook, even though the potato is sitting on a cold plate.

In your company, a Davar Gush is any high-impact, high-density asset, executive, or legacy system that carries its own "heat" (influence, risk, power) wherever it goes, completely bypassing your organizational boundaries.

Consider these organizational Davar Gush examples:

1. The Toxic Star Performer: You have a co-founder or an early engineer who is incredibly brilliant but treats people terribly. You decide to "move them out of the main line of fire" by placing them in an isolated R&D silo or a secondary project team (Kli Sheni). You think you have insulated the rest of the company. But because they are a Davar Gush—a dense mass of historical authority and critical technical knowledge—they carry their toxic heat directly into that new team. They don't cool down. They continue to "cook" everyone they interact with, despite the structural buffer you built.
2. The Legacy Codebase: Your original, un-refactored monolithic code is a Davar Gush. It was built fast and loose in the early days (Kli Rishon). You decide to wrap it in clean, modern microservices (Kli Sheni) to isolate the risk. But because that legacy core is dense and poorly documented, any minor change or integration passed to it immediately triggers a cascading system failure. It retains its volatile heat, cooking your new infrastructure.
3. A Massive, Concentrated Customer: If 60% of your revenue comes from one enterprise client, that client is a Davar Gush. You can build all the customer success buffers and account management layers you want (Kli Sheni), but when that client demands a feature or throws a tantrum, their direct heat penetrates your entire organization. They bypass your product roadmap, stress out your engineering team, and dictate your strategy just as if they were sitting in your boardroom (Kli Rishon).

The lesson of the Davar Gush is that structural insulation is an illusion when dealing with high-density variables. You cannot neutralize a high-risk asset simply by moving it down the org chart or wrapping it in a secondary process. If it is solid, dense, and hot, it will cook wherever it lands. You must either cool it down at the core, break it up into smaller pieces, or remove it from the system entirely.

---

Policy Move

To operationalize the thermodynamics of the Arukh HaShulchan, you must transition from passive risk management to an active Thermal Delegation Audit (TDA).

This policy ensures that before your company delegates any high-energy objective (sales, growth, data acquisition, moderation) to a secondary system or partner, you evaluate the "heat" of the incentives and the vulnerability of the target environment.

The Thermal Delegation Protocol

Every department head initiating a third-party partnership or deploying an automated system must complete a TDA. The audit evaluates three key metrics, directly derived from the halachic thermodynamics of Orach Chaim 318:

               [THERMAL DELEGATION AUDIT (TDA)]
                              │
       ┌──────────────────────┼──────────────────────┐
       ▼                      ▼                      ▼
 [Incentive Temp]     [Target Vulnerability]  [Asset Density]
(Yad Soledet Bo)         (Kaleh HaBishul)      (Davar Gush)
       │                      │                      │
       ▼                      ▼                      ▼
Is commission/KPI      Does target lack       Does partner operate
excessive? (>30% of    resources/power to     with unchecked
market average)        resist bad actors?     systemic access?

Step 1: Measure the "Incentive Temperature" (Determining Yad Soledet Bo)

You must evaluate the thermal energy of the incentives you are passing to the secondary vessel.

• High-Heat Indicators: Commission-only sales structures, hyper-aggressive SLA penalties for customer support, or automated algorithms optimized solely for click-through rates without safety guardrails.
• The Rule: If your incentive structure is so intense that the partner or system cannot survive without cutting corners (their hand is "scorched" by the pressure), the incentive temperature is classified as Yad Soledet Bo.

Step 2: Map the "Target Vulnerability" (Identifying Kaleh HaBishul)

Identify the medium upon which this secondary partner or system will act.

• Vulnerability Indicators: Are they interacting with non-technical users, handling sensitive PII, or operating in a grey regulatory zone?
• The Rule: If the target environment cannot withstand indirect heat without undergoing a catastrophic state change (loss of trust, regulatory probe, data leak), it is classified as Kaleh HaBishul. High-heat incentives are strictly prohibited from interacting with these targets.

Step 3: Identify the "Solid Masses" (Managing the Davar Gush)

Determine if any partner, executive, or tool has been granted unchecked systemic access or disproportionate leverage.

• Density Indicators: An outsourced agency that owns your entire marketing infrastructure, or a high-performing VP who has sole access to your primary database.
• The Rule: These entities must be treated as Kli Rishon (direct liability). They cannot be insulated by contracts or managerial layers. They must be subject to direct, weekly executive oversight.

Concrete Implementation: The Thermal Risk Retention (TRR) Ratio

To measure the effectiveness of this policy, your risk and compliance team will track the Thermal Risk Retention (TRR) Ratio quarterly.

$$\text{TRR Ratio} = \frac{\text{Vendor/System Spend with "High Heat" Incentives}}{\text{Total Vendor/System Spend}}$$

• High Heat is defined as any contract where more than 30% of the compensation is tied to variable, high-pressure KPIs (e.g., volume-based outbound, low-cost customer resolution metrics), or any automated system running without human-in-the-loop validation.
• Target Benchmark: Your TRR Ratio must remain under 15%. Any department exceeding a 15% TRR Ratio must present a mitigation plan to the executive team, either by restructuring the vendor contract to include flat-fee components (cooling down the Kli Rishon) or by implementing automated compliance filters to protect vulnerable targets (Kaleh HaBishul).

---

Board-Level Question

"What is our organizational Davar Gush, and how are we pretending our secondary vessels insulate us from its heat?"

To make this question concrete for your next board meeting, present the following diagnostic matrix to your directors and executive team:

┌──────────────────────────────┬──────────────────────────────┬──────────────────────────────┐
│  Potential "Davar Gush"      │  The "Secondary Vessel" Illusion│  The Thermodynamic Reality   │
├──────────────────────────────┼──────────────────────────────┼──────────────────────────────┤
│  Toxic High-Performer        │  "We moved them to an        │  They carry their influence  │
│  (e.g., Brilliant VP/Eng)    │  isolated R&D silo."         │  and continue to cook culture│
├──────────────────────────────┼──────────────────────────────┼──────────────────────────────┤
│  Fragile Legacy Codebase     │  "We wrapped it in modern    │  Any minor integration       │
│  (Early-stage tech debt)     │  microservices."             │  triggers cascading failures │
├──────────────────────────────┼──────────────────────────────┼──────────────────────────────┤
│  Concentrated Customer       │  "We assigned a dedicated    │  They bypass roadmaps and    │
│  (>40% of ARR)               │  CS manager to buffer them." │  dictate company strategy    │
└──────────────────────────────┴──────────────────────────────┴──────────────────────────────┘

This question is designed to cut through the structural denial that plagues scaling startups.

When a company experiences an ethical or operational crisis, the executive team's first instinct is almost always to point to their organizational chart or their vendor agreements. They show the board the compliance reports, the segregated Slack channels, or the outsourced service agreements. They argue, “See? We built a wall. We put the risk in a Kli Sheni. We didn't think the heat would transfer.”

As a board, you must challenge this defense. You must force the leadership team to identify the dense, solid masses within the enterprise that defy these artificial boundaries.

If your head of sales is generating incredible numbers but systematically destroying the product team's morale, they are a Davar Gush. You cannot "manage" them by putting them in a different room. Their heat is too dense; it will cook your product roadmap anyway.

If your core database is built on shaky, un-audited customer data, that data is a Davar Gush. You cannot insulate it by building clean APIs around it. The moment you run an analysis or share that data with a partner, the regulatory heat will transfer, and you will be burned.

By forcing the board to confront this question, you shift the governance focus from structural compliance (which looks good on paper but fails in practice) to thermodynamic reality (which actually governs how risk and influence flow through your company).

---

Takeaway

In the physical world, heat does not care about your intentions. It only cares about conductivity, density, and mass.

In the business world, ethical risk behaves exactly the same way. You cannot delegate your way out of moral or operational liability. If you set up high-pressure incentives, that heat will travel through your contracts, through your APIs, and through your outsourced teams. If it encounters a vulnerable market, an unprotected database, or a fragile team culture, it will cook them.

Do not rely on the illusion of the secondary vessel. Map your heat sources. Identify your raw eggs. Dismantle your solid masses before they burn your entire house down. Build a company that doesn't just look compliant on paper, but is thermodynamically cool, stable, and built to last.