Arukh HaShulchan, Orach Chaim 265:7-12

Hook

You're a founder. You're moving fast, breaking things, and constantly pushing boundaries. The question isn't if you'll outsource, automate, or delegate to gain speed and market share, but how aggressively. You’ve got a competitive landscape that doesn't sleep, and every advantage counts. So, when does "smart delegation" or "efficient automation" cross into "ethical sidestepping"? When does benefiting from a third-party's less-than-ideal practices become your problem?

It’s tempting to draw a neat line: "If I didn't explicitly tell them to do it, it's not on me." Or, "If the system runs automatically, the code is the problem, not my ethical oversight." This kind of thinking is a short-term sugar rush, followed by a long-term ethical hangover. Regulatory fines, PR disasters, talent drain – these aren't just hypothetical risks; they're the market's brutal feedback loop for ethical negligence. This isn't about being "nice"; it's about building a resilient, defensible business. Today, we're cutting through that noise with ancient wisdom that makes modern sense.

Text Snapshot

The Arukh HaShulchan, a foundational legal code, meticulously details the prohibition of working on Shabbat (the Sabbath). It extends this prohibition beyond direct action:

• You cannot start a task you know won't finish before Shabbat, even if technically permissible.
• You can let automatic processes (like a mill) continue if started before Shabbat.
• Crucially, you cannot instruct a non-Jew to perform work for your benefit on Shabbat, nor can you benefit from work a non-Jew performs on your property or object, even if they act independently, if you knew they would perform work.
• However, saving a life (Pikuach Nefesh) overrides these restrictions.

Analysis

Insight 1: Fairness - Due Diligence is Non-Delegable

Let's be clear: your ethical perimeter extends far beyond your direct employee roster. The Arukh HaShulchan hammers this home, stating, "If one gives a non-Jew an object to take care of for him, and the non-Jew performs work upon it... this is forbidden." (Orach Chaim 265:10). It continues, "If one instructs a non-Jew to perform work for him, even if he performs it for free, it is forbidden for a Jew to derive benefit from it." (265:10).

The Founder Takeaway: You cannot outsource your ethical responsibility. Period. When you contract out your manufacturing, engage a third-party data processor, or even simply provide a platform where others operate, any ethical shortcuts they take for your benefit become your liability. The text explicitly prohibits benefiting from work performed by a proxy if that work would be forbidden for you. This isn't just about legality; it's about fundamental fairness. If your customers or partners are unknowingly impacted by ethically dubious practices in your supply chain, or if your cost advantage comes from exploiting labor or data through a third party, that's a fairness issue that will eventually hit your bottom line.

Decision Rule for Fairness: "Benefit by Proxy equals Responsibility by Proxy." If you benefit, you're responsible. This means proactive due diligence isn't a "nice to have" but a core operational requirement. You must ensure your partners, contractors, and even automated systems operate within your ethical framework, not just their local legal minimums. The risk of brand damage, regulatory fines, and customer churn from ethically compromised supply chains or data practices far outweighs the perceived cost savings.

Insight 2: Truth - No Ethical Arbitrage Through Proxies

Founders are masters of finding efficiencies and optimizing processes. But there's a fine line between optimization and ethical arbitrage – leveraging technicalities or proxies to bypass the spirit of a rule. The Arukh HaShulchan is explicit: "If one began a task before sunset on Friday that he cannot complete before sunset, even if it is a task which is not forbidden... it is forbidden to continue it." (Orach Chaim 265:7). Furthermore, it warns, "If one gives a non-Jew a gift, and it is known that the non-Jew will perform work on it, it is forbidden." (265:10).

The Founder Takeaway: This isn't just about direct instruction. It's about foresight and intent. If you know a process, even if initiated innocently, will lead to an ethically problematic outcome, you're obligated to prevent it. If you 'gift' a task to a third party, fully aware they'll perform it in a way you couldn't or shouldn't, that's not clever; it's deceptive. This applies to so-called "grey areas" in data privacy, aggressive marketing tactics outsourced to agencies, or even product features designed to exploit cognitive biases, especially if those features are developed by third-party teams. You can't claim ignorance or hide behind a technicality when the ethical outcome was predictable.

Decision Rule for Truth: "Intent Trumps Technicality." Your business operations must align with the spirit of ethical conduct, not just the bare letter of the law. If your strategy relies on exploiting loopholes or using proxies to achieve an outcome you wouldn't directly endorse, you're building on shaky ground. Transparency and genuine ethical alignment, even when it means foregoing a short-term advantage, build trust – the ultimate currency in today's market. Misleading practices, even by proxy, erode that trust faster than you can acquire new users.

Insight 3: Competition - Proactive Ethical Design & Foresight

Every founder understands the pressure to launch, to iterate, to capture market share. But the Arukh HaShulchan introduces a critical dimension to this hustle: foresight. "If one began a task before sunset on Friday that he cannot complete before sunset... it is forbidden to continue it." (Orach Chaim 265:7). The emphasis here is on knowing in advance and preventing the violation. You don't get a pass for starting something with good intentions if you neglected to consider its inevitable unethical conclusion.

The Founder Takeaway: Ethical considerations aren't a post-launch patch; they're integral to your product and process design. You must proactively anticipate ethical pitfalls, especially when building automated systems or engaging in competitive practices. If your algorithm, designed for efficiency, inadvertently creates unfair biases, or if your growth hacking strategy, when scaled, leads to privacy violations, it's because the ethical guardrails weren't designed in from the start. Building fast without building ethically is a race to the bottom, especially in competitive landscapes where ethical lapses are quickly weaponized by rivals or scrutinized by regulators. Gaining a competitive edge by cutting corners on ethical design leads to technical debt that compounds into ethical debt.

Decision Rule for Competition: "Build Ethical Guardrails, Not Afterthoughts." Design your products, algorithms, and business processes with ethical foresight. Ask not just "Can we do this?" but "Should we do this, and what are the predictable ethical externalities?" This proactive stance isn't just defensive; it can be a significant competitive differentiator. Companies known for robust ethical design attract top talent, earn deeper customer loyalty, and are more resilient against competitive attacks based on ethical grounds.

Policy Move

Policy: Third-Party & Automated System Ethical Impact Assessment (EIA)

We will implement a mandatory Ethical Impact Assessment (EIA) for all new third-party engagements (e.g., suppliers, contractors, agencies, platform partners) and any significant new automated systems or AI deployments.

Process:

1. Pre-Engagement/Pre-Deployment Review: Before signing contracts or deploying, a cross-functional team (legal, product, operations, ethics lead) must complete an EIA. This assessment will identify potential ethical risks, including but not limited to labor practices, data privacy, environmental impact, bias, and transparency, based on the principles of "Benefit by Proxy" and "Intent Trumps Technicality."
2. Ethical Clause Integration: All third-party contracts will include explicit ethical compliance clauses, mandating adherence to our company's ethical code, not just local legal minimums. These clauses will grant us audit rights and specify termination conditions for ethical breaches.
3. Ongoing Monitoring & Audit: For critical third parties and automated systems, we will establish a schedule for regular ethical audits and performance reviews. This includes spot checks, anonymous feedback channels, and technical audits for algorithms to detect drift or unintended consequences.
4. Remediation & Escalation: Clear protocols for identifying, addressing, and escalating ethical violations will be established, ensuring swift action and transparent communication, both internally and externally where appropriate.

KPI Proxy: "Third-Party Ethical Compliance Score" (TPECS). This will be an aggregate score (0-100) calculated annually, based on the percentage of critical suppliers/contractors passing their ethical audits, the number of unresolved ethical flags from automated system EIAs, and the time-to-resolution for identified ethical issues. Our target is a TPECS of 90+ for all critical partners and systems.

Board-Level Question

"Given our aggressive growth targets and increasing reliance on global third-party contractors, suppliers, and AI-driven automation, how are we quantitatively measuring and proactively mitigating the indirect ethical and reputational risks that could manifest as brand damage, regulatory fines, or talent attrition? Specifically, how confident are we that our current oversight mechanisms address the Arukh HaShulchan's principle that 'benefit by proxy' is effectively 'responsibility by proxy,' preventing ethical arbitrage in our pursuit of competitive advantage?"

This question forces leadership to move beyond superficial compliance checks. It demands a strategic discussion on the systemic risks embedded in our current operational model. It challenges the assumption that ethical responsibility stops at our organizational chart and pushes for a proactive, measurable approach to managing the ethical footprint of our entire value chain and technological stack. The board needs to understand that ignoring indirect ethical liabilities isn't "risk management"; it's deferred catastrophe. The ROI isn't just about avoiding penalties; it's about building a reputation for integrity that attracts and retains the best talent, customers, and investors.

Takeaway

Your ethical perimeter extends far beyond your direct control. The moment you start benefiting from a third party or an automated system, their ethical footprint becomes yours. Design for this reality proactively, or prepare to pay the price reactively, both in financial terms and in the invaluable currency of trust.