Arukh HaShulchan Yomi · Startup Mensch · Standard
Arukh HaShulchan, Orach Chaim 310:7-12
Hook
You just closed your Series A. Your bank account is flush, and your immediate instinct is to scale defenses. You hire a hyper-specialized PhD in machine learning at a eye-watering salary to build a proprietary model. You purchase a high-end enterprise database license with strict access controls. You buy specialized hardware that sits in a dedicated server rack. You tell your team: “This is our core IP. Don’t touch it, don’t mess with it, and don't use it for anything other than its designated, high-stakes purpose.”
You think you are protecting your assets. You think you are mitigating risk.
In reality, you have just committed a classic startup sin: you have created organizational Muktzah.
In Jewish law, Muktzah refers to items that are "set aside" and forbidden to be moved or handled on Shabbat. A specific, highly restrictive subcategory is Muktzah Machmat Chisaron Kis—items set aside because of potential monetary loss. These are tools so specialized, fragile, or expensive that the owner absolutely refuses to use them for any task other than their primary, designated function. Because the owner is so meticulous about preserving their value, the law deems these tools completely "untouchable."
As a founder, you do this constantly. Out of fear of depreciation, disruption, or failure, you isolate your most valuable assets—whether they are software systems, specialized talent, or proprietary data. You lock them in intellectual silos, making them functionally untouchable to the rest of your team. When a market shift demands an immediate, all-hands-on-deck pivot, you find yourself paralyzed. Your most expensive resources cannot be repurposed because you have systematically trained your organization to treat them as fragile, single-use relics.
To survive in a hyper-competitive landscape, you cannot afford to freeze your capital in sacred silos. You must understand how subjective anxiety transforms dynamic assets into operational liabilities. The Arukh HaShulchan provides the precise legal and psychological framework needed to dismantle these silos, unlock resource versatility, and maintain the operational liquidity required to scale.
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
"והטעם בזה, מפני שכל דבר שאינו כלי, או שהוא כלי שמלאכתו לאיסור ואינו ראוי לטלטל לצורך גופו ומקומו, הרי הוא מוקצה... ומהו מוקצה מחמת חסרון כיס? אלו דברים שמקפיד עליהם שלא להשתמש בהם כלל תשמיש אחר... מפני שעל ידי תשמיש אחר יפחת דמיהם, ונמצא שמקצה דעתו מהם לגמרי..."
"And the reason for this is that anything which is not a vessel, or is a vessel whose primary work is forbidden and is not fit to be moved for its own sake or for its place, is muktzah... And what is 'muktzah due to monetary loss'? It refers to items that one is meticulous about, preventing their use for any other purpose... because any alternative use would diminish their value. Consequently, the owner removes his mind from them entirely..." — Arukh HaShulchan, Orach Chaim 310:7
Analysis
Insight 1: The Principle of Subjective Siloing (Truth)
The core mechanism of Muktzah Machmat Chisaron Kis is not determined by an objective market price, but by the subjective anxiety of the owner. In Arukh HaShulchan, Orach Chaim 310:7, the author explains that an object is set aside "because one is meticulous about them (she'makpid alav) preventing their use for any other purpose." This meticulousness (kapdanut) is born out of fear: the owner worries that "by any alternative use, their value will diminish."
In startup operations, this is the exact psychological mechanism that drives the siloing of high-value assets. When you hire an elite specialist or purchase a high-tier enterprise software suite, your subjective fear of "depreciating" or "breaking" that asset causes you to restrict its utility. You tell your junior engineers, “Do not touch the core production codebase; only the lead architect can touch it.” Or you instruct your marketing team, “Do not run experimental campaigns on our primary domain; we cannot risk our domain authority.”
While these boundaries seem like prudent risk management, Arukh HaShulchan, Orach Chaim 310:7 reveals the hidden cost of this behavior: "the owner removes his mind from them entirely (nemtza she-maktzeh da'ato mehem legamri)." By designating an asset as too valuable to be used for anything other than its hyper-specialized task, you mentally write off its broader utility. You create an operational blind spot.
When you remove your mind from an asset's alternative utilities, you lose the ability to see how that asset could solve adjacent, existential business problems. If your lead architect is treated as a delicate, single-use asset who cannot be bothered with basic bug fixes or customer support escalations during a product crisis, you have effectively rendered them "untouchable." The truth of your business is that your survival depends on asset liquidity. If your subjective anxiety causes you to silo your resources, you are artificially restricting your company's operational capacity based on fear, not on reality.
Insight 2: The Fallacy of Intrinsic Value (Fairness)
It is easy to assume that if an asset is highly valuable, it must automatically be treated with extreme caution and isolated from common use. The Arukh HaShulchan flatly rejects this assumption. In Arukh HaShulchan, Orach Chaim 310:8, the text notes:
"For if you do not say so, then any valuable vessel would be muktzah, which is not the case; for we see that one may move valuable gold and silver vessels..."
The law distinguishes between high objective value and subjective isolation. A solid gold goblet is highly valuable, yet it is not muktzah because the owner does not mind using it for ordinary drinking. The value of the asset does not dictate its restriction; only your refusal to use it for common tasks does.
This is a critical lesson in organizational fairness and resource allocation. Founders often create double standards by treating expensive hires or "rockstar" departments as elite, golden vessels that are too precious to engage in common operational tasks. You exempt your top-tier AI researchers from writing basic documentation, or you shield your enterprise sales team from assisting with customer retention efforts during a churn crisis.
This creates a toxic cultural divide and operational fragility. According to Arukh HaShulchan, Orach Chaim 310:8, the moment you allow an expensive asset to be used for common tasks, it loses its restricted status. It becomes part of the active, mobile inventory of the household.
To run a fair and resilient company, you must apply this rule to your team. No hire, regardless of their salary or pedigree, should be a "golden vessel" exempt from the common, unglamorous work of survival. If your $250k/year engineer refuses to jump on a customer support call when the system goes down, they are an isolated asset. By forcing all assets—regardless of their cost—to maintain a degree of general utility, you ensure that your capital is deployed fairly and efficiently across the entire organization.
Insight 3: The Agility of Intentional Dual-Use (Competition)
In a highly competitive market, speed and adaptability are your only real advantages. If your competitor can repurpose their assets faster than you can, they will win. The Arukh HaShulchan addresses how to prevent an asset from becoming locked down, pointing to the power of pre-emptive designation.
In Arukh HaShulchan, Orach Chaim 310:10, the text discusses tools that are designed for forbidden work (e.g., a professional tool used for crafting), but can be moved if they are needed for a permitted purpose (e.g., using a heavy professional hammer to crack open nuts). However, if the tool is so delicate that the owner would never use it for such a common task, it remains muktzah and cannot be moved under any circumstances.
The legal pivot occurs in Arukh HaShulchan, Orach Chaim 310:12, which explains that if the owner explicitly prepares or designates the specialized tool for a common, alternative use before the restricted period begins, they successfully strip it of its restricted status. The act of pre-emptive designation changes the ontological status of the tool.
This is your competitive playbook. If you want to maintain a highly agile startup, you must pre-emptively build "dual-use" designations into your most specialized and expensive assets. You cannot wait for a market crisis to figure out how to repurpose your proprietary tech stack or your specialized team members.
By documenting and testing alternative use cases for your high-value assets before you need them, you keep them "mobile." If your proprietary data-scraping infrastructure is primarily used for your core consumer app, you must pre-emptively design it so that it can also feed your B2B lead-generation engine if the consumer market softens. If your lead designer is hyper-focused on product UX, you must ensure they spend 10% of their time on marketing collateral. This pre-emptive designation, as formulated in Arukh HaShulchan, Orach Chaim 310:12, ensures that when a crisis hits, you do not lose precious weeks trying to break down operational silos. Your assets are already legally and functionally mobile, ready to be deployed to the area of greatest competitive need.
Policy Move
The Dual-Utility Audit and Mobility Protocol (DUMP)
To prevent organizational Muktzah and ensure your startup’s assets remain fluid, you must implement a formal policy that outlaws single-use silos for any resource costing over a specific threshold.
Policy Objective
To systematically audit every high-cost asset (defined as any software license, hardware infrastructure, or headcount costing >$100,000/year) and establish a documented "Common Utility Path" to ensure operational mobility during a pivot or crisis.
Step-by-Step Execution
[ IDENTIFY HIGH-VALUE ASSETS ]
(Cost >$100k/yr or critical path)
│
▼
[ DEFINE PRIMARY & SECONDARY USE ]
(Primary task vs. Common utility)
│
▼
[ CONDUCT THE "MUKTZAH TEST" ]
(Does fear of damage/cost block alternative use?)
┌────┴────┐
YES NO
│ │
▼ ▼
[ REDUCE FRICTION ] [ APPROVE ASSET ]
(Build guardrails, cross- (Document in
train, automate recovery) Asset Registry)
The Asset Registry and Threshold Identification
Every quarter, the finance and engineering teams will co-author an Asset Registry. Any asset—whether it is an enterprise SaaS subscription, an API, a physical server, or an employee’s salary—that exceeds $100,000 annually must be flagged.The "Muktzah Test"
For each flagged asset, the department head must answer the following question based on the principle in Arukh HaShulchan, Orach Chaim 310:7:
“Is this asset currently protected with such meticulousness (kapdanut) that we would refuse to deploy it or its owner to a basic, cross-functional task during an operational emergency?”
If the answer is yes, the asset is designated as "Restricted" and must undergo immediate remediation.Formulating the Common Utility Path (CUP)
Consistent with Arukh HaShulchan, Orach Chaim 310:12, every Restricted asset must have a written, actionable "Common Utility Path."- For Talent: A specialized machine learning engineer must have a documented secondary role (e.g., writing automated QA tests or assisting with backend API maintenance) and must spend at least 4 hours per sprint executing tasks in this secondary domain. This prevents them from becoming an untouchable, specialized "vessel."
- For Software/Infrastructure: Any high-cost database or proprietary software tool must have a documented secondary use case (e.g., using a high-cost analytics engine to process raw marketing data during a campaign push, rather than reserving it solely for product analytics).
- For IP/Codebases: No repository may have a "single-editor" lock. At least two other engineers must be cross-trained to deploy hotfixes to that repository, eliminating key-man Muktzah.
Friction Reduction and Guardrails
If the fear of "depreciation" or "damage" (the chisaron kis mentioned in Arukh HaShulchan, Orach Chaim 310:7) is legitimate—such as a junior engineer breaking a production database—the policy demands that you build technical guardrails (e.g., automated staging environments, robust roll-back scripts, or sandbox accounts) rather than isolating the asset. You solve the risk with engineering, not with siloing.
Metric/KPI Proxy: The Asset Liquidity Index (ALI)
To measure the effectiveness of this policy, track your Asset Liquidity Index (ALI) quarterly:
$$\text{ALI} = \frac{\text{Number of High-Value Assets with an Active, Tested CUP}}{\text{Total Number of High-Value Assets (> $100k/year)}}$$
- Target KPI: $\ge 90%$
- Why this matters: If your ALI drops below 90%, it means your company is accumulating operational debt. You are locking up too much capital in specialized, fragile silos, leaving you highly vulnerable to market shocks.
Board-Level Question
"Which of our 'sacred cow' assets are we currently over-protecting to the point of operational paralysis, and what is the carrying cost of this self-imposed restriction?"
Context for the Board
As board members, your primary fiduciary duty is to manage risk and protect the company’s valuation. However, there is a distinct difference between safeguarding an asset and freezing it. Often, boards push founders to implement hyper-restrictive security policies, silo intellectual property, or isolate key executives from day-to-day operations under the guise of "protecting the IP."
This board-level question is designed to challenge the assumption that isolation equals protection.
When we look at Arukh HaShulchan, Orach Chaim 310:9, the text highlights a profound psychological reality: when an owner is terrified of even a minor financial loss on an asset, they "remove their mind" from it, rendering it completely useless for anything else. The fear of a 5% depreciation in value results in a 100% loss of utility during the restricted period.
In the startup world, this is the equivalent of protecting your IP so aggressively that your team cannot iterate on it, or guarding your key-man dependencies so tightly that your executive team is paralyzed without them.
Strategic Implications to Raise in the Boardroom
- The Carrying Cost of Idle Capital: If we have purchased software licenses or hired talent that can only be utilized for one highly specific project, we are carrying massive overhead that cannot assist us during a market pivot. We must calculate the opportunity cost of this idle capacity.
- The Key-Man Liability: If our technical co-founder is the only person allowed to access our deployment pipeline because we are afraid of security breaches or code degradation, we have created a massive point of failure. We must ask: Is our security posture protecting us, or is it paralyzing our engineering velocity?
- The Pivot Stress Test: If we had to change our business model tomorrow due to a sudden regulatory shift or competitor move, how many of our current assets could be repurposed within 48 hours? If the answer is "very few" because our tools and talent are too specialized, then our valuation is built on a foundation of sand.
By forcing the board to confront this question, you shift the conversation from defensive preservation to dynamic liquidity. You help your investors understand that the ultimate risk mitigation is not siloing your assets, but ensuring they are versatile enough to survive any market condition.
Takeaway
In the high-stakes game of building a venture-backed startup, you cannot afford to let fear dictate your resource allocation. The laws of Muktzah Machmat Chisaron Kis teach us that when we treat our most valuable assets with over-protective anxiety, we do not preserve them—we freeze them. We remove our minds from their broader utility and turn them into static liabilities.
Do not let your expensive software, your elite talent, or your proprietary technology become untouchable relics. Break down the silos. Implement the Dual-Utility Audit. Force every "golden vessel" in your company to maintain a common, practical utility.
By keeping your assets mobile, versatile, and integrated, you ensure that when the market tests your company, you will not be paralyzed by your own defenses. You will be agile, liquid, and ready to win.
derekhlearning.com