Mishneh Torah, Sabbath 9

Hook

You’re a founder building in the "gray zone." You have a product that isn't quite finished, or a process that’s half-optimized. You tell yourself: It’s not perfect, but it works well enough to ship. Or, perhaps you’re looking at a competitor’s feature and thinking, If I just iterate on their foundation, I’m not really "stealing"—I’m just finishing what they started.

The Maimonidean perspective on Sabbath labor—specifically the laws of cooking (bishul)—is the ultimate startup audit. It forces you to confront the "minimum viable" trap. In the Mishneh Torah, Rambam defines liability not just by the final product, but by the contribution to the process. When you bring the fire, the wood, or the water, you are liable for the result.

Founders often hide behind the "it wasn't my final commit" defense. Rambam dismantles this: if your action is a necessary link in a chain that produces a prohibited result, you are fully accountable for the whole. Whether you are "cooking" a market, a product, or a P&L, you cannot outsource your ethics to the complexity of the workflow. The real founder dilemma isn't whether you "finished" the job; it’s whether your piece of the process sets the inevitable, irreversible momentum in motion.

Text Snapshot

"A person who bakes [an amount of food] the size of a dried fig is liable... A person who places an egg next to a kettle so that it will become slightly cooked is liable... When one person brought fire, another brought wood... another put in spices, and another stirred it, all are liable for cooking. For anyone who performs an activity that is necessary for cooking is considered as [having performed that forbidden labor]." (Mishneh Torah, Sabbath 9:1–6)

Analysis

Insight 1: The Liability of the "Enabler"

In the startup world, we often talk about "distributed responsibility." When a project fails or a product causes harm, we point fingers: "The engineer wrote the code, but the PM defined the spec, and the designer made it look good." Rambam rejects this diffusion of responsibility. The text explicitly notes, "When one person brought fire, another brought wood... all are liable for cooking."

Decision Rule: If you provide the "catalyst" (the fire) or the "fuel" (the wood) for a project that you know will result in an ethical compromise, you are not a bystander. You are a co-conspirator. As a founder, you must audit your supply chain and your internal workflows not just for output, but for the inputs you authorize. If your team is "stirring" a pot that shouldn't be on the stove, your hands are in the soup.

Insight 2: The "Dried Fig" of Materiality

Rambam is obsessed with shiurim (minimum measures). Baking a "dried fig’s size" triggers liability. In business, we call this the "materiality threshold." Many founders operate with the illusion that if a transgression is small—a little data scraping here, a minor misrepresentation of ARR there—it doesn't count.

Decision Rule: Don't confuse "insignificant" with "immaterial." The law teaches that once a threshold is crossed, the entirety of the labor is accounted for. If you justify a "small" ethical shortcut, you are liable for the full scale of the operation it supports. If your KPI is growth, define your "dried fig"—the moment at which an activity shifts from "experimental" to "permanent" (or "liable"). Once you hit that, you are fully on the hook.

Insight 3: Derivative Labor is Still Labor

The text states, "A person who melts even the slightest amount of metal... performs a derivative [of the forbidden labor] of cooking." This destroys the "it's not the same thing" loophole. Founders often argue that their specific tactic (e.g., aggressive tax avoidance, dark patterns in UI) isn't "technically" lying or "technically" illegal.

Decision Rule: Functionality trumps nomenclature. If your "derivative" activity produces the same outcome as the prohibited primary activity, you are guilty of the same infraction. If your "growth hack" functions like theft, you are a thief. If your "optimization" functions like deception, you are a liar. Stop hiding behind industry jargon—call the outcome by its real name.

Policy Move

Implement the "Common Kettle" Audit. Most product teams operate in silos where the "fire-bringer" never talks to the "wood-bringer." Establish a monthly "Sabbath Audit" (or "Integrity Audit") where each department head must declare their current "kettle."

• The Process: Every feature or growth initiative must be mapped against an "Intent-to-Impact" matrix. If a feature (e.g., an automated upselling loop) is identified as potentially predatory, the "stirrers" (product designers) and the "fire-bringers" (leadership) must sign off on the ethical liability.
• The Change: If any participant in the chain cannot defend the ethics of the final "cooked" product, the "fire" is pulled. You no longer allow departments to argue that their specific commit was neutral. If the total process is questionable, every participant is held responsible for the entire project’s pivot or termination.

Board-Level Question

"Looking at our current growth trajectory, which of our 'derivative' activities—those small, seemingly innocuous operational shortcuts we take every day—would be considered 'liable' if we had to justify them to a regulator under the strictest interpretation of our own internal integrity code? And if we know these activities are 'cooking' the numbers or the market, why are we still fueling the fire?"

Takeaway

Liability in business is not about intent; it is about the completeness of the process. You are not just responsible for your "commit"; you are responsible for the fire you ignited, the wood you provided, and the soup you stirred. If you are building a company, you are "cooking" reality. Ensure that what you are serving is something you’d be willing to eat yourself.

KPI Proxy: Ethical Debt Ratio = (Number of "Gray Zone" operational shortcuts) / (Total team capacity). If this ratio trends upward, you are effectively "cooking" on the Sabbath of your company’s integrity. Keep it at zero.