Arukh HaShulchan, Orach Chaim 311:3-8

Hook

Every seasoned founder has a closet full of ghosts: the joint venture that quietly expired but remains on the books, the legacy codebase that no engineer will touch but still runs critical user flows, or the co-founder who was sidelined eighteen months ago but still holds a board seat and an active email address.

These are your corporate "corpses." They are inert, non-functional, and legally or reputationally hazardous to touch. In the language of startup operations, we call them legacy liabilities or zombie assets. In the language of Halakha, they are muktzeh—items set aside and forbidden to be handled on the Sabbath because they serve no active, permissible purpose.

The natural instinct of a cash-strapped, hyper-focused founder is to ignore these dead assets. "We’ll deal with the clean-up after the Series B," you tell yourself. "It's not hurting anyone just sitting there."

But it is.

Leaving a dead project, a failed partnership, or an inactive executive to rot in silence is not a neutral act. It drains emotional bandwidth, muddies your cap table, creates security vulnerabilities, and slowly degrades your brand’s integrity. The longer a dead asset is exposed to the harsh light of the market, the more toxic it becomes. It begins to emit a reputational odor that alerts investors, competitors, and top-tier talent that your house is not in order.

The dilemma is acute: how do you move, bury, or transition a highly sensitive, toxic, or legally frozen asset when touching it directly risks triggering a lawsuit, a public relations disaster, or a covenant breach? How do you clean up the mess without violating your ethical obligations to your stakeholders or your legal agreements with your creditors?

The Arukh HaShulchan, writing on the laws of handling a corpse on Shabbat, provides an extraordinarily sophisticated operational framework for this exact scenario. It teaches us how to move what is technically "unmovable" by utilizing strategic bundling (kikar o tinok—a loaf of bread or a child) and indirect manipulation (tiltul min hatzad). This isn’t about deceptive corporate maneuvering; it is about high-integrity, compliant engineering designed to preserve human dignity and corporate viability under intense pressure.

---

Text Snapshot

The following passage from the Arukh HaShulchan outlines the legal mechanisms permitted to move a deceased person on Shabbat to prevent decomposition and maintain human dignity.

אורח חיים שׁי״א:ג׳ מֵנִיחַ עָלָיו כִּכָּר אוֹ תִּינוֹק וּמְטַלְּלוֹ... וְהַטַּעַם שֶׁהִתִּירוּ לְטַלְטֵל עַל יְדֵי כִּכָּר אוֹ תִּינוֹק, מִפְּנֵי שֶׁכְּבוֹד הַבְּרִיּוֹת חָבִיב וְהֶחֱמִירוּ בְּבִזָּיוֹן הַמֵּת...

אורח חיים שׁי״א:ה׳ וְאִם אֵין לוֹ כִּכָּר אוֹ תִּינוֹק... מְטַלְּלוֹ מִן הַצַּד, דְּהַיְנוּ שֶׁמְּהַפְּכוֹ מִמִּטָּה לְמִטָּה אוֹ מְגַלְגְּלוֹ...

אורח חיים שׁי״א:ז׳ וְדַע דְּלֹא הִתִּירוּ לְטַלְטֵל עַל יְדֵי כִּכָּר אוֹ תִּינוֹק אֶלָּא לְמֵת בִּלְבַד מִפְּנֵי כְּבוֹד הַמֵּת, אֲבָל לִשְׁאָר דְּבָרִים הָאֲסוּרִים בְּטִלְטוּל... לֹא הִתִּירוּ...

Translation and Context

Orach Chaim 311:3 One places a loaf of bread or a child upon [the corpse] and moves it... And the reason they permitted moving it by means of a loaf or a child is because human dignity (kavod habriot) is precious, and [the Sages] were stringent regarding the disgrace of the deceased...

Orach Chaim 311:5 And if he does not have a loaf or a child... he moves it indirectly (tiltul min hatzad), meaning that he flips it from bed to bed or rolls it...

Orach Chaim 311:7 And know that they did not permit moving by means of a loaf or a child except for a corpse alone because of the dignity of the deceased; but for other things that are forbidden to be moved... they did not permit [this mechanism]...

---

Analysis

Operating a high-growth startup requires a constant confrontation with failure. Yet, while Silicon Valley loves to fetishize "failing fast," it rarely discusses the mechanics of cleaning up fast. When a project dies, we are often paralyzed by the technical, legal, and relational debt it leaves behind.

The Arukh HaShulchan’s analysis of Shabbat laws provides three profound operational insights for managing this debt, categorized as decision rules for the modern founder.

Insight 1: The "Loaf or Child" Principle (Operational Bundling)

The core halakhic mechanism described in Arukh HaShulchan, Orach Chaim 311:3 is the use of a kikar (a loaf of bread) or a tinok (a child) to permit the movement of a corpse. A dead body is muktzeh—it cannot be moved on Shabbat because it has no utility on this holy day. However, a loaf of bread (which is food) or a child (who is a living being) are highly permitted (mutar) to be handled. By placing the permitted item on top of the forbidden one, the corpse becomes auxiliary (tafel) to the living or useful item. When you lift the bundle, your primary intent and halakhic justification is the movement of the permitted item, and the dead asset is moved along with it.

This is not a deceptive "hack." It is a highly structured, transparent legal framework designed to resolve a direct clash between two competing values: the rabbinic prohibition of handling muktzeh and the severe ethical breach of exposing a human body to public degradation (kavod habriot).

In a startup, your "corpse" might be an outdated, failing product line that is draining server costs and exposing you to security vulnerabilities, but which you cannot shut down because a handful of legacy enterprise clients have lifetime contracts. Touching the product—modifying the code, changing the terms of service—triggers legal liabilities or customer outrage.

The decision rule here is Operational Bundling: You do not attempt to move or sunset the dead asset in isolation. Instead, you build a "living" bridge. You construct an upgraded, highly valuable new product feature (the "loaf" or "child") and package it alongside the migration path.

You go to the legacy clients and say: "We are launching our next-generation infrastructure, which includes advanced security and 10x speed (the living asset). As part of this transition, we are migrating all legacy accounts to this new environment and deprecating the old system."

By bundling the dead asset's retirement with a high-utility, value-additive offering, you transform a hostile negotiation into a customer success win. You are legally and operationally moving the "dead" code under the banner of delivering the "living" product.

[Dead Asset / Corpse (Muktzeh)] 
       + 
[Value-Add / Loaf of Bread (Mutar)] 
       │
       ▼
[Unified Transition Bundle] ───> Dignified, Compliant Migration

Insight 2: Tiltul Min Hatzad (Indirect Friction Management)

What happens if you do not have a "loaf or a child"? What if there is no budget to build a new feature, no sweet transition package to offer, and you are left with a raw, unmitigated liability?

The Arukh HaShulchan address this in Arukh HaShulchan, Orach Chaim 311:5:

"And if he does not have a loaf or a child... he moves it indirectly (tiltul min hatzad), meaning that he flips it from bed to bed or rolls it..."

Tiltul min hatzad is the act of moving a forbidden object using an indirect physical force—like using your elbow, or tilting a surface so the object rolls. You are not gripping the muktzeh item with your hands. You are changing the environment around it to achieve the necessary movement.

In corporate governance, founders frequently encounter situations where direct intervention is blocked. Consider a toxic, non-performing board member or early investor who holds veto rights over your next funding round. You cannot fire them directly; their shares are protected by a robust shareholder agreement. Directly confronting them or trying to strip their rights (direct handling) will trigger a catastrophic litigation cycle that will kill the company.

The decision rule is Indirect Friction Management: You must move the obstacle by altering the environment around it. Instead of a direct, head-on legal assault, you utilize indirect structural moves:

1. Board Expansion: You don't remove the toxic board member; you expand the board from three seats to five, appointing two highly sophisticated, independent directors who neutralize the toxic member's voting power.
2. Re-incorporation / Flip-Up: You establish a new parent entity in a different jurisdiction (e.g., Delaware) to facilitate a new investment round, structured in a way that legally dilutes or restructures the voting rights of legacy, non-cooperative shareholders, forcing them into a passive position without breaching your fiduciary duties.
3. Operational Re-routing: If a legacy vendor is failing but you are locked into a multi-year contract with heavy termination penalties, you do not breach the contract. Instead, you spin up a parallel, optimized workflow using a new vendor and gradually reduce your API calls or data volume to the legacy vendor to the absolute minimum allowed under the contract's Minimum Commitments.

You are not touching the "corpse" directly. You are tilting the bed so that it rolls into a position where it can no longer harm the company's vital organs.

Insight 3: The Heat of the Sun & Kavod HaBriot (The Cost of Inaction)

Why does the Arukh HaShulchan allow these complex maneuvers in the first place? Why not just leave the corpse where it is until Shabbat ends?

The text is explicit:

"...because human dignity (kavod habriot) is precious, and [the Sages] were stringent regarding the disgrace of the deceased..." Arukh HaShulchan, Orach Chaim 311:3.

The specific scenario envisioned by the Sages is a body lying in the hot sun. Left unattended, the heat will accelerate decomposition, causing physical degradation and a foul odor that disgraces the deceased and torments the living.

This is highly relevant on this day, Rosh Chodesh Tamuz. The month of Tamuz marks the onset of the summer season (Tekufat Tamuz), characterized by intense, blazing heat. It is a time of maximum exposure, where things left out in the open rot quickly. Historically, Tamuz is associated with the cracking of walls and the exposure of vulnerabilities (the breaching of the walls of Jerusalem).

In business, the "sun" is the market. It is the public eye, the gossip columns, the backchannels of venture capital, and the glassdoor reviews of your employees. When you leave a dead initiative, a failed product, or an unresolved founder dispute "in the sun" during a market downturn or a highly competitive season, the decay is rapid and highly visible.

The Arukh HaShulchan points out a critical distinction in Arukh HaShulchan, Orach Chaim 311:7:

"And know that they did not permit moving by means of a loaf or a child except for a corpse alone because of the dignity of the deceased; but for other things... they did not permit [this]."

If you lose a purse full of gold on Shabbat, you cannot use the "loaf or child" trick to save your money. Why? Because financial loss does not override the sanctity of Shabbat laws in the same way that human dignity (kavod habriot) does. The Sages recognized that human dignity is a non-negotiable, supreme ethical value that justifies extraordinary legal leniencies.

Translate this directly to your startup's cap table and team structure: People are not financial assets.

When an executive fails, or when you must lay off 20% of your team, you are dealing with human dignity. If you handle layoffs poorly—slashing access to Slack at 6:00 AM with no warning, offering insulting severance packages, or leaving terminated employees to twist in the wind while you write a self-serving blog post—you are leaving a "corpse in the sun." The resulting reputational rot will destroy your ability to recruit top talent for years.

The decision rule is Dignity Over Convenience: The cost of reputational and human degradation is exponentially higher than the operational friction required to execute a clean, dignified exit. You must expend the capital, the time, and the creative legal energy to ensure that every departure, every sunset project, and every corporate restructuring is handled with absolute respect and class. You do not leave your failures to rot in the public square.

---

Policy Move

To operationalize these insights, your startup must implement a formal Zombie Asset Sunset Protocol (ZASP). The goal of this protocol is to transition inactive, toxic, or legacy assets out of the active operational sphere without triggering legal, technical, or reputational crises.

This protocol is triggered whenever an asset (a product, a code repository, a contract, or an executive relationship) is classified as Dormant & High-Liability (DHL)—the corporate equivalent of a corpse in the sun.

[Trigger: Asset Classified as DHL]
               │
               ▼
┌──────────────────────────────────────────────┐
│  Phase 1: The Muktzeh Audit                  │
│  - Map direct & indirect liabilities         │
│  - Identify regulatory & covenant blocks     │
└──────────────────────┬───────────────────────┘
                       │
                       ▼
┌──────────────────────────────────────────────┐
│  Phase 2: The "Loaf or Child" Bundling       │
│  - Identify active, high-value "living" asset│
│  - Package legacy transition with new value  │
└──────────────────────┬───────────────────────┘
                       │
                       ▼
┌──────────────────────────────────────────────┐
│  Phase 3: The Tiltul Min Hatzad Execution    │
│  - If bundling fails, apply environmental shift│
│  - Re-route workflows, expand boards, dilute │
└──────────────────────┬───────────────────────┘
                       │
                       ▼
┌──────────────────────────────────────────────┐
│  Phase 4: Dignified Burial (Kavod HaBriot)    │
│  - Secure offboarding, fair severance        │
│  - Clean public communication, no lingering rot│
└──────────────────────────────────────────────┘

Phase 1: The Muktzeh Audit

Every quarter, the leadership team must review all dormant assets. Ask:

• Is this asset generating revenue or utility?
• Does keeping this asset alive expose us to security breaches, contractual litigation, or brand degradation?
• Are we forbidden from touching or altering this asset directly due to existing covenants, investor rights, or regulatory restrictions?

If the asset has no utility but cannot be easily removed, it is classified as DHL.

Phase 2: The "Loaf or Child" Bundling Strategy

For every DHL asset, the product or legal team must identify a "living" asset to carry it.

• Technical Debt: If deprecating an old API will break legacy integrations, bundle the deprecation with the launch of a highly anticipated, free developer tool or a robust SDK that makes migration painless.
• Customer Contracts: If you must terminate a low-margin, high-maintenance client segment, partner with a friendly competitor. Offer the clients a seamless, white-glove migration to the partner’s platform, complete with a transition discount funded by a revenue-share agreement with that partner. You move the liability (the unprofitable clients) by bundling it with a highly attractive alternative (the discount and white-glove service).

Phase 3: The Tiltul Min Hatzad (Environmental Shift)

If no bundling option exists, legal and operations must design an indirect route.

• Failing Partnerships: If a joint venture partner is unresponsive but holds intellectual property rights that block your product roadmap, do not sue. Instead, design around the blocked IP, or restructure your operational workflow so that the blocked technology is rendered obsolete by your new, proprietary architecture. You have moved the company forward by shifting the technical landscape, leaving the dead partnership harmlessly isolated.

Phase 4: Dignified Burial (Kavod HaBriot)

When shutting down an entity, terminating a department, or parting ways with a founder, execute with maximum dignity.

• Severance & Support: Provide outplacement services, generous severance, and clean, mutually agreed-upon public narratives.
• Prompt Communication: Do not let rumors fester in the "summer heat" of slack channels. Communicate changes swiftly, transparently, and with deep empathy.

Key Metric: Time-to-Burial (TTB)

To measure the effectiveness of your ZASP, track your company’s Time-to-Burial (TTB).

$$\text{TTB} = \text{Date of Asset Classification as DHL} - \text{Date of Complete Safe Sunset/Migration}$$

• Target TTB: $< 45 \text{ days}$ for operational/technical assets; $< 15 \text{ days}$ for human resource or leadership transitions.
• Why this matters: A high TTB means your organization is allowing toxic assets to rot in the sun, draining executive focus, driving up legal risk, and exposing your team to cultural decay. Keeping TTB low preserves organizational energy and market reputation.

---

Board-Level Question

As a founder, you cannot execute these high-stakes maneuvers in a vacuum. You need your board's alignment, particularly when dealing with "corpses" that involve cap table restructuring, executive transitions, or major product deprecations.

At your next board meeting, present this strategic question to your directors:

"What is currently our most significant 'corpse in the sun'—the legacy contract, failing product line, or historical governance structure that we are avoiding due to legal or relational friction—and what 'living asset' or indirect structural shift must we design to execute a dignified, compliant wind-down before the market forces a catastrophic exposure?"

Unpacking the Board's Role

This question is designed to cut through the standard, highly polished board deck narratives and force a raw, realistic assessment of the company's liabilities.

1. Overcoming the Sunk Cost Fallacy

Board members are often highly resistant to burying dead assets because they represent historical capital allocation. If the company spent $3M developing a proprietary database architecture that is now obsolete and causing stability issues, board members may push to "keep optimizing it."

By framing the issue through the lens of Arukh HaShulchan, Orach Chaim 311:3, you refocus the board on the existential risk of reputational and operational rot. You must convince them that the cost of keeping the dead asset alive (the "smell" in the sun) is vastly higher than the write-off required to bury it.

2. Evaluating the Legal Risks of Direct vs. Indirect Action

Your board's legal counsel will naturally advise caution. They will tell you all the reasons why you cannot terminate a toxic partner or dilute a non-cooperative shareholder.

This is where you introduce the distinction between direct handling and tiltul min hatzad (indirect movement). Present the board with highly structured, creative legal paths—such as reverse tri-party mergers, board seat expansions, or parallel IP development—that achieve the necessary business outcome without breaching fiduciary duties or triggering litigation.

3. Protecting the Brand's Human Capital

A truly founder-friendly board understands that the ultimate driver of long-term ROI is the company's culture and talent brand. If the board pushes for a brutal, cost-cutting layoff to preserve cash for the next three months, you must stand firm on the principle of Kavod HaBriot (human dignity).

Use the halakhic distinction in Arukh HaShulchan, Orach Chaim 311:7: we do not bend the rules of dignity for mere financial preservation ("a purse of gold"), but we must do so for human life and respect. Show the board that a cold, undignified layoff will destroy internal morale and permanently damage your employer brand, resulting in a net-negative return on investment when the market recovers and you need to scale again.

---

Takeaway

In the relentless heat of the startup journey—especially as we navigate the reflective, high-exposure season of Tamuz—the measure of your leadership is not just how many new initiatives you launch, but how cleanly and honorably you bury your dead.

Do not let your legacy failures, toxic relationships, or outdated systems rot in the public square. Apply the wisdom of the Arukh HaShulchan:

• Bundle your liabilities with active, high-utility value drivers (kikar o tinok).
• Shift the environment when direct confrontation is blocked (tiltul min hatzad).
• Prioritize human dignity above operational convenience (kavod habriot).

By mastering the art of the clean, dignified sunset, you protect your cap table, preserve your team’s focus, and ensure that your startup remains a clean, high-performance vehicle built for long-term scale. Keep your house in order, keep your balance sheet clean, and never let your corpses rot in the sun.