Mishneh Torah, Sabbath 9

Hook

In the modern startup ecosystem, we are obsessed with "The MVP"—the Minimum Viable Product. We are conditioned to believe that if a feature isn’t fully polished, or if a product isn’t "done" by the standards of the market, it doesn't count. We chase the release date, the launch party, and the final state of perfection. We treat business as a binary: either the product is live and generating revenue, or it is a draft.

But the Rambam’s Mishneh Torah, Sabbath 9 shatters this binary. He introduces a high-stakes, uncompromising framework for liability that ignores our obsession with "end states" and instead focuses on the incremental contribution to a final result. Whether it is cooking, dyeing, or weaving, the law teaches us that liability isn't just about the finish line; it is about the act of contribution.

"When one person brought fire, another brought wood... another put in meat, another put in spices, and another stirred it, all are liable for cooking."

For a founder, this is a terrifying, clarifying realization. In your company, you likely suffer from a diffusion of responsibility. When a launch fails, or a product breaks, or an ethical line is crossed, you hear the "I just did my part" defense. A developer says, "I just wrote the code, I didn't set the server." A marketing lead says, "I just drafted the copy, I didn't promise the feature."

This text forces a radical accountability shift. In the eyes of the law, if you contributed a necessary component to the final outcome, you are not a bystander—you are the architect of the result. You are liable.

As a founder, you need to decide: are you running a company where people hide behind the "smallness" of their individual tasks, or are you building a culture where everyone recognizes that they are part of a singular, irreversible process of creation? If you want to scale, you must stop letting your team segment their morality. Every small "fig-sized" action you take is, in fact, the act of cooking the whole.

Analysis

Insight 1: The Principle of Cumulative Liability (The "Composite" Rule)

The Rambam is explicit: "A person who places meat over coals, and a portion the size of a dried fig becomes [thoroughly] roasted, he is liable even when the portions that are roasted are [separate, and located] in two or three portions."

In business, we often treat "small" failures or "minor" ethical shortcuts as non-issues because they don't reach a "threshold of significance." We think, as long as the product isn't totally broken, the minor bug is fine. Or, as long as the data privacy breach is only on a small subset of users, it’s not a full-scale disaster.

The Torah rejects this. It teaches that impact is cumulative. If your small, seemingly insignificant errors or compromises aggregate to the size of a "dried fig"—a standard of total impact—you are fully liable for the damage.

Decision Rule: Stop evaluating your team’s output by individual task performance. Evaluate by aggregate outcome. If you have ten employees each cutting a small, "harmless" corner on quality or truth, you have a massive, systemic integrity failure. The "fig-sized" rule forces you to audit the sum of your company’s behavior, not just the isolated performance of its parts.

Insight 2: The "Derivative of Fire" (Indirect Impact)

The text notes: "A person who places an egg next to a kettle so that it will become slightly cooked is liable... for a person who cooks with a derivative of fire is considered as if he cooked with fire itself."

This is the ultimate lesson on systemic consequences. Founders often convince themselves they are not responsible for the downstream effects of their algorithms or business models because they didn't "directly" cause the harm. They say, "We just built the platform; we didn't force the users to behave that way."

The Rambam says: If you generate the heat, you are responsible for what gets cooked. If you create a culture of extreme pressure, you are responsible for the burnout, even if you never explicitly told an employee to work 100 hours. If you build a viral loop that exploits human psychology, you are responsible for the addiction, even if you didn't "directly" force the user to click.

Decision Rule: You are liable for the derivative heat of your product. If you create a mechanism that facilitates a specific outcome—whether it's market manipulation, toxic user behavior, or employee burnout—you are the one cooking the pot. Do not hide behind the "indirectness" of the mechanism.

Insight 3: The Completion Threshold (The "Ben D'rosai" Test)

The text discusses the Ma'achal Ben D'rosai, the point at which food is cooked enough to be eaten. "If the entire [piece of meat] becomes half-cooked... one is liable."

This is a profound insight into product-market fit and ethical maturation. There is a point in every project where the "cooking" is sufficient that the product is functional. Once it is functional, it attracts liability. You cannot claim "it’s still in beta" if it is already "edible" (functional) for the public.

Decision Rule: Beta is not a shield for negligence. The moment your product provides value (is "eaten"), it has reached a threshold of maturity where it must be fully compliant, ethical, and stable. If you are shipping "half-cooked" products to gain market share, you are legally and ethically liable for the state of that product. Don't wait for "version 1.0" to start taking responsibility; the moment it solves a problem for a customer, you are fully on the hook.

Policy Move

The "Shared Liability Ledger" Policy

To move from an abstract concept to a concrete process, implement the Shared Liability Ledger (SLL) for all high-stakes product releases and strategic decisions.

Currently, your team operates in silos where the "bringer of wood" doesn't see the "bringer of fire." This policy mandates that before any major feature release or pivot, every contributor (engineering, product, legal, marketing, sales) must sign off on a document that explicitly lists the cumulative risks.

1. The Registry: For every feature, list the "ingredients." (e.g., Codebase, Data Source, Marketing Promise).
2. The Attribution: Each contributor must acknowledge: "I am a contributor to this 'cooking' process."
3. The "Derivative Heat" Audit: The team must answer one question: "If this feature performs exactly as intended, what is the 'cooked' outcome for our most vulnerable user?"
4. The Veto: Any contributor can pause the "cooking" process if they identify that the aggregate impact exceeds the company's ethical "dried fig" threshold.

This shifts the culture from "I just did my job" to "We are all responsible for the final meal." It forces the marketing team to understand the technical risks and the developers to understand the consumer-facing promises. By making everyone a co-owner of the "fire," you ensure that the total output is vetted by the collective conscience of the team, not just the founder.

Board-Level Question

"Are we currently 'cooking' something that is functionally 'eatable' by the public, while we still insist on treating it as 'raw' or 'in-development' to avoid accountability?"

This question forces the board to confront the gap between the company's marketing narrative (the "beta" excuse) and the reality of the product’s impact. If the board admits that the product is already being used in a way that generates real-world consequences, they must immediately pivot to a stance of full professional and ethical accountability. If they are still hiding behind "experimental" status to excuse poor quality or ethical shortcuts, they are failing their fiduciary duty to mitigate risk.

Takeaway

The Rambam teaches us that in the economy of action, there are no "minor" contributions. Whether you are the one who starts the fire or the one who stirs the pot, the result is your own.

KPI Proxy: Total Error Aggregation (TEA). Track the number of "small" issues/bugs/ethical deviations per feature release. If your TEA rises, your culture is leaking accountability. Don't look for the person who broke the build; look for the "kitchen" that allowed the process to become careless.

Mensch Moment: Stop saying "it’s just a bug" or "it’s just a growth hack." If it feeds the growth of your company, it’s a meal you’ve cooked. Own the recipe.