Arukh HaShulchan Yomi · Startup Mensch · Standard
Arukh HaShulchan, Orach Chaim 311:15-22
Hook
Every venture-backed founder eventually inherits a corpse.
It isn’t a physical body, but the operational equivalent: a dead-weight asset you cannot easily dispose of without triggering a catastrophic event. It is the co-founder who checked out two years ago but still sits on your cap table with 15% common stock. It is the legacy codebase that is a security liability but runs your core billing engine, making it too dangerous to touch. It is the failed pivot—the product line you spent $4M of your Series A to build, which now sits completely idle, generating zero revenue but costing $40k a month in hosting and compliance overhead to maintain because of a legacy enterprise SLA.
In the high-stakes pressure cooker of scaling a startup, these "dead assets" create profound paralysis. If you touch them, you risk triggering a lawsuit, a tax audit, a board revolt, or a public relations disaster. If you leave them alone, they rot. They drain your team’s focus, eat up cash flow, and emit a toxic odor that ruins company culture and scares off future investors.
This is the exact operational tension that Rabbi Yechiel Michel Epstein addresses in the Arukh HaShulchan, Orach Chaim 311:15-22. Written in the late 19th century—a period of massive economic transition—this text deals with a highly visceral, high-stakes dilemma: how to handle a human corpse (met) on Shabbat. Under Jewish law, a corpse is muktzeh—it is legally categorized as an object that cannot be moved or handled on the day of rest.
But a dead body does not wait for Shabbat to end. It may be lying in the blazing sun, accelerating its decay. It may be in a public space, creating an acute crisis of human dignity (Kavod HaBriot). It might be trapped in a burning building where leaving it feels like an act of desecration, yet carrying it out violates the core laws of the Sabbath.
How do you navigate a rigid regulatory framework when leaving a dead asset untouched causes systemic rot, but moving it directly violates the letter of the law?
As a founder, you are constantly told that you must choose between two bad options: blind compliance with legacy structures that kills your company’s momentum, or reckless rule-breaking that exposes you to existential liability. The Arukh HaShulchan rejects this binary. It offers a masterclass in pragmatic ethics, showing how to use structured legal workarounds, prioritize human dignity over physical assets, and recognize the exact moment when internal technical debt becomes an external reputational emergency.
Let's look at the text and extract the operational playbook for your startup’s dead weight.
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
ארוך השולחן, אורח חיים שס״א:ט״ו "...מֵת הַמֻּטָּל בַּחַמָּה וּמִתְיָרֵא שֶׁמָּא יַסְרִיחַ, מַנִּיחַ עָלָיו כִּכָּר אוֹ תִּינוֹק וּמְטַלְטְלוֹ... וְהַטַּעַם: מִפְּנֵי כְּבוֹד הַבְּרִיּוֹת שֶׁלֹּא יִתְבַּזֶּה הַמֵּת."
ארוך השולחן, אורח חיים שס״א:י״ח "...אִם הִסְרִיחַ כְּבָר, וְאֵין הַכִּכָּר אוֹ הַתִּינוֹק מוֹעִיל לְשַׁכֵּךְ אֶת הַבִּזָּיוֹן, מְטַלְטְלוֹ אֲפִילּוּ בְּלֹא כִּכָּר וְתִינוֹק, דְּגָדוֹל כְּבוֹד הַבְּרִיּוֹת שֶׁדּוֹחֶה אֶת הַשַּׁבָּת בְּאִסּוּרֵי דְּרַבָּנָן."
ארוך השולחן, אורח חיים שס״א:כ״א "...אֲבָל לְהַצִּיל הַמֵּת מִן הַדְּלֵיקָה... אָסוּר לְטַלְטְלוֹ אֶלָּא עַל יְדֵי כִּכָּר אוֹ תִּינוֹק... דְּהַצָּלַת מָמוֹן קַלָּה יוֹתֵר מִכְּבוֹד הַמֵּת."
Analysis
[ STARTUP CRISIS ]
│
┌────────────────────┴────────────────────┐
▼ ▼
[ Operational Inertia ] [ Reputational Decay ]
(Muktzeh / Sunlit Corpse) (Srichah / Foul Odor)
│ │
┌──────────┴──────────┐ ┌────────┴────────┐
▼ ▼ ▼ ▼
[ Bundling Action ] [ Legal Fiction ] [ Direct Action ] [ Radical Pivot ]
(Kikar u'Tinok) (Strategic M&A) (Emergency Move) (Dignity Over Cash)
Insight 1: The Anatomy of the Ethical Loophole (Kikar u'Tinok)
In Arukh HaShulchan, Orach Chaim 311:15, we encounter a classic halachic mechanism:
"מֵת הַמֻּטָּל בַּחַמָּה וּמִתְיָרֵא שֶׁמָּא יַסְרִיחַ, מַנִּיחַ עָלָיו כִּכָּר אוֹ תִּינוֹק וּמְטַלְטְלוֹ" (If a corpse is lying in the sun and one fears it will decay/smell, one places a loaf of bread or a child upon it and moves it.)
To the modern, secular eye, this looks like a ridiculous legal trick. How does placing a loaf of bread on top of a dead body suddenly make it permissible to move an object that is strictly forbidden to be touched?
But this is not a trick; it is a highly structured legal fiction. In halacha, a corpse is muktzeh machmat gufo—it has no intrinsic utility on Shabbat, so handling it is forbidden. A loaf of bread or a living child, however, is fully permitted to be moved. By placing the permitted item on the forbidden one, you create a unified operational unit where the primary intent of the movement is directed toward the permitted item (kikar or tinok), and the corpse is moved only incidentally (tiltul min hatzad).
In the startup world, you will constantly face situations where direct, brute-force action is blocked by legal, regulatory, or cap-table constraints.
- You cannot simply fire a toxic, non-performing co-founder who holds 15% of the company's equity without triggering a lawsuit that could freeze your next funding round.
- You cannot easily shut down a failed legacy product line because a single, highly litigious enterprise client has an ironclad service-level agreement (SLA) that runs for another three years.
If you move the "corpse" directly, you violate the rules of the game and destroy your company.
The ethical founder does not throw up their hands in defeat, nor do they break the law. Instead, they design a "Kikar u'Tinok"—an elegant, structured workaround that bundles the dead asset with a living, high-value asset to facilitate its movement.
For example, instead of trying to strip the toxic co-founder of their shares directly (which triggers the lawsuit), you execute a recapitalization or a structural corporate reorganization. You create a new corporate entity to house your active, high-growth intellectual property (the "child" or "bread") and merge the old entity into it. The toxic co-founder’s shares are diluted or converted under standard, legally defensible valuation metrics. You did not move the dead weight to destroy it; you moved the living asset, and the dead asset was restructured as an incidental byproduct of that legitimate growth move.
The same applies to failed product lines. You do not breach the contract and face damages. You bundle the legacy software's maintenance into a broader, high-value migration package that transitions the legacy client to your new, modern platform for free. You use the "living" product to carry the "dead" product out of your active codebase.
The ethical boundary here is clear: the workaround must serve a real, constructive purpose. You cannot use a legal fiction to defraud. In halacha, the loaf of bread or the child must be something you actually intend to use or care for; you cannot use a piece of garbage as your kikar. Your business restructuring must hold genuine commercial substance, not just be a paper sham designed to squeeze someone out.
Insight 2: The Inflection Point of Reputational Decay (Srichah)
The Arukh HaShulchan recognizes that legal fictions have their limits. What happens when the situation deteriorates past the point of elegant workarounds?
In Arukh HaShulchan, Orach Chaim 311:18, Rabbi Epstein writes:
"אִם הִסְרִיחַ כְּבָר, וְאֵין הַכִּכָּר אוֹ הַתִּינוֹק מוֹעִיל לְשַׁכֵּךְ אֶת הַבִּזָּיוֹן, מְטַלְטְלוֹ אֲפִילּוּ בְּלֹא כִּכָּר וְתִינוֹק" (If it has already decayed/smelled, and the loaf or child is no longer sufficient to mitigate the disgrace, one may move it even without a loaf or child.)
This is a massive halachic concession. The Arukh HaShulchan is outlining an inflection point of decay. When a corpse begins to decompose (srichah), it emits a foul odor that causes active, public embarrassment (bizayon) to the living and the dead. At this exact moment, the requirement for a legal workaround is dropped. The preservation of human dignity (Kavod HaBriot) is so vital that it overrides the rabbinic prohibition of muktzeh directly. You do not look for a loaf of bread anymore; you grab the body and move it out of the room immediately.
Every startup has an internal clock running on its unresolved crises.
- A technical debt issue (e.g., a known security vulnerability in your database) is initially a "sunlit corpse." It is dormant, but if you leave it there, it will eventually rot.
- A toxic executive who quietly harasses junior employees is a dormant corpse. You try to manage them out slowly, using HR "workarounds" (like shifting their reporting lines or hiring an executive coach—your business equivalent of a kikar).
But there comes a point where the situation "smells" (hisriach).
- The database is breached, and customer data is actively leaking onto the dark web.
- The toxic executive’s behavior goes public on social media, or a formal lawsuit is filed, threatening to destroy your company’s reputation.
When the smell hits, the time for clever, slow-moving legal workarounds is over. You cannot afford the luxury of "bundling" or running a slow HR process. You must take direct, aggressive, and immediate action to clear the rot, even if it violates standard operating procedures, breaks your budget, or causes short-term pain with your board.
Many founders fail because they do not recognize this inflection point. They try to apply "Kikar u'Tinok" (a slow, polite workaround) to a situation that is already decomposing in public. If your database is actively leaking, you don’t write a polite email asking your engineering team to schedule a patch for next sprint. You shut down the servers immediately, accept the temporary downtime (which violates your SLAs), and fix the leak.
The ethical rule of thumb here is simple: The moment an internal risk transitions into public disgrace or active harm, your priority shifts from procedural compliance to radical damage control.
Insight 3: The Hierarchy of Crisis: Dignity vs. Capital Preservation
In Arukh HaShulchan, Orach Chaim 311:21, the text draws a sharp distinction between saving a corpse from a fire and saving physical property:
"אֲבָל לְהַצִּיל הַמֵּת מִן הַדְּלֵיקָה... אָסוּר לְטַלְטְלוֹ אֶלָּא עַל יְדֵי כִּכָּר אוֹ תִּינוֹק... דְּהַצָּלַת מָמוֹן קַלָּה יוֹתֵר מִכְּבוֹד הַמֵּת." (But to save a corpse from a fire... it is forbidden to move it except via a loaf or a child... for saving money/property is treated more leniently than preserving the dignity of the dead.)
This is a profound ethical hierarchy. Rabbi Epstein argues that if a fire breaks out on Shabbat, your instinct to save your physical assets (your money, your inventory) is highly restricted. You cannot violate Shabbat laws to save your cash. But when it comes to saving a human body from being burned—even though the person is already dead—the concern for human dignity is so intense that we allow the use of the kikar u'tinok workaround to rescue the body from the flames.
Yet, if you cannot find a workaround, you cannot violate the Sabbath directly just to save property. The preservation of human dignity (even post-mortem) ranks higher than the preservation of capital.
In a startup crisis, founders almost always invert this hierarchy.
When a company is going under, or when a massive market shift occurs, the founder's primary panic is usually financial: How do we save our runway? How do we protect the cap table? How do we keep our venture capitalists happy? In their rush to save the "money," they treat their people as disposable assets. They conduct brutal, cold layoffs over a 3-minute Zoom call with no severance, disable Slack access instantly, and treat former team members like security threats. They burn their human capital to save a few weeks of cash runway.
The Arukh HaShulchan demands a different hierarchy of values.
Your team members, your customers, and your community are the "human lives" of your ecosystem. Even when a project is "dead"—when you are shutting down a division or winding down the entire company—the preservation of their dignity (Kavod HaBriot) must take precedence over the raw preservation of capital.
If you must wind down a product line, you do not just pull the plug overnight to save on hosting costs, leaving your customers stranded and their businesses disrupted. You give them a soft landing, export their data, and help them migrate to a competitor.
If you must lay off staff, you do not optimize solely for cash preservation. You offer fair severance, keep their healthcare active for as long as possible, and actively help them find new roles.
Yes, this costs money. Yes, it reduces your remaining runway. But according to Torah ethics, preserving human dignity is an absolute operational requirement, while preserving capital is a secondary concern.
A founder who saves $100k by humiliating their departing team has not won; they have compromised their soul and built an ethical liability that will haunt their next venture. Investors talk, talent talks, and the market remembers how you treat people when the building is on fire.
Policy Move
To operationalize the teachings of the Arukh HaShulchan, your startup must implement an Operational Sunset & Dignity Protocol (OSDP). This policy ensures that when a product, partnership, or employment relationship dies, it is handled with structured transparency, legal compliance, and radical human dignity—rather than being left to rot or handled via deceptive workarounds.
[ SUNSET TRIGGER EVENT ]
│
▼
[ Phase 1: The Smell Test ]
Is this asset actively decaying?
├── YES ──► Execute Direct Public Resolution (No Workarounds)
└── NO ──► Proceed to Phase 2
│
▼
[ Phase 2: The Bundling Audit ]
Can we structure a clean, transparent legal workaround?
├── YES ──► Bundle with active value (Kikar u'Tinok)
└── NO ──► Execute clean, dignified termination
│
▼
[ Phase 3: The Dignity Guarantee ]
Prioritize people over capital preservation.
└── Allocation of "Dignity Severance" & Data Off-ramps
1. The "Smell Test" Audit (Monthly)
Every department head must submit a monthly "Zombie Asset & Risk Report." This report categorizes outstanding liabilities into two buckets:
- Sunlit Corpses (Dormant Risks): High technical debt, legacy contracts, underperforming employees, or unresolved cap table disputes. These are managed via structured, proactive workarounds (e.g., performance improvement plans, structured contract renegotiations, software refactoring sprints).
- Decaying Assets (Active Odors): Security vulnerabilities actively exploited, toxic employee behavior with multiple reports, or products violating compliance laws. These bypass all standard procedures and go straight to the executive committee for immediate, direct resolution within 48 hours, regardless of the immediate financial cost.
2. The Transparent Bundling Guideline (Kikar u'Tinok Rule)
When restructuring a business unit, settling a cap table dispute, or sunsetting a product, any "legal fiction" or structural workaround must pass the Transparency Test:
- The workaround must have independent commercial substance. If you are merging entities or recapitalizing to clean up a cap table, the new entity must have a distinct, documented business plan and real operational utility.
- You cannot bundle a completely dead, valueless asset with a living one to mislead an acquirer or investor. If you are selling a package of IP, you must explicitly disclose the operational status of all bundled assets.
3. The Dignity Guarantee (Capital vs. People)
In the event of a layoff, wind-down, or major pivot, the company commits to a minimum Dignity Runway:
- Severance Floor: A minimum of 4 weeks of severance pay and 2 months of continued healthcare coverage for any laid-off employee, regardless of tenure, to be prioritized over preserving cash for non-essential marketing or software SaaS subscriptions.
- The Soft Landing SLA: For any sunsetted product, customers must be given a minimum of 90 days' notice, a free automated tool to export 100% of their data, and a documented recommendation list for alternative providers.
Key Metric: Crisis Decay Velocity (CDV)
To track the effectiveness of this policy, your executive team will monitor the Crisis Decay Velocity (CDV):
$$\text{CDV} = \text{Date of Public Disclosure/Resolution} - \text{Date of Internal Detection}$$
Your goal is to keep CDV under 14 days for "Decaying Assets" and to ensure that no "Sunlit Corpse" remains unresolved on your risk register for more than 90 days before a structured workaround is executed.
Board-Level Question
The Setup
At the next board meeting, your lead investor is likely to push you to cut costs to extend your runway. They might look at your engineering team and say, "We need to lay off 20% of the staff immediately. Lock their laptops over the weekend, send them a generic email, and don't offer severance beyond the statutory minimum. We need to save every penny of cash to hit our next milestone."
They might also look at a product line that is failing but still has active users and say, "Just turn off the servers. The contract says we can terminate for convenience with 30 days' notice, but if we just shut it down today, we save $15k in hosting this month. Let them sue us; they won't spend the money on lawyers."
This is the moment to stand up as a Torah-guided, ROI-minded leader. You must reframe the conversation from short-term cash preservation to long-term risk mitigation and reputational equity.
The Strategic Question to Ask Your Board
"If we burn our human capital and customer trust to save 45 days of cash runway, what is the exact cost to our brand equity, our future recruiting velocity, and our next funding round when the 'smell' of this transition hits the market? Are we structuring this wind-down with enough dignity to preserve our long-term ability to operate, or are we treating our reputation as a disposable asset?"
The Business Case (The ROI of Dignity)
Explain to your board that a sloppy, undignified layoff or product shutdown is not a cost-saving measure; it is a high-interest loan taken against your company's future.
- Recruiting Cost: When you treat departing employees poorly, your Glassdoor rating plummets, your remaining team's morale collapses, and your voluntary turnover rate spikes. Replacing a single top-tier software engineer costs an average of $150k in recruiting fees and onboarding time. If three key engineers quit because they are disgusted by how their peers were treated, you have wiped out any savings from the severance cuts.
- Sales Cycle Drag: If you abruptly shut down a product and leave customers stranded, that story will find its way to Reddit, Hacker News, and your competitors' sales decks. A single public post about how you abandoned your users can extend your enterprise sales cycle by 3-6 months, as prospects demand complex escrow agreements and financial audits before signing with you.
- Investor Brand: Top-tier founders do not want to work with venture capitalists who force their portfolio companies to act dishonorably. By insisting on a dignified off-ramp, you protect not only your brand but also the reputation of the fund backing you.
Takeaway
The Arukh HaShulchan teaches us that we cannot always avoid crises, failures, or the accumulation of "dead weight" in our businesses. Skeletons will enter the closet; products will fail; co-founder relationships will break down.
But as a founder, your job is not to pretend these corpses don't exist, nor is it to let them rot until they ruin your company.
You must act with the precision of a halachic scholar:
- Use structured, transparent workarounds (Kikar u'Tinok) to move dead assets before they cause damage.
- Recognize the inflection point of decay (Srichah) and take immediate, direct action when an issue threatens your public integrity.
- Prioritize human dignity (Kavod HaBriot) over cash preservation.
When you build a company that values its people and its reputation more than its paper valuation, you create an organization that can survive any fire. You build a brand that talent wants to work for, that customers trust, and that investors want to back.
Do not let your dead assets rot your living company. Clean up the mess, pay the price of dignity, and keep moving forward.
derekhlearning.com