Mishneh Torah, Sabbath 14

Hook

The modern founder’s nightmare isn’t just competition; it’s the lack of boundaries. We live in a world of "always-on" connectivity where your Slack, your living room, and your strategy sessions bleed into one another until you lose the ability to distinguish between high-leverage deep work (a private domain) and the chaotic, low-value noise of the marketplace (a public domain).

In Mishneh Torah, Sabbath 14, Rambam dissects the four domains of human activity. He isn't just teaching Sabbath law; he is teaching spatial intelligence. He defines a "private domain" (the space where you exert authority) and a "public domain" (where you are subject to the crowd). For a startup, if you don't define the boundaries of your "private domain"—your core IP, your focus, your culture—you are effectively carrying your most valuable assets into the "public domain" of market noise, where they lose their protected status. You’re leaking value because you’ve failed to build the "walls" of 10 handbreadths that distinguish your proprietary edge from the commodity environment.

Text Snapshot

"There are four domains... a private domain, a public domain, a carmelit, and a makom patur." "What constitutes a private domain? A place that is surrounded by four walls that are [at least] ten handbreadths high..." "The space above a private domain until [the highest point] in the heavens is considered a private domain." "It is permitted to carry throughout a private domain... In contrast, one may carry only within [a square of] four cubits in a public domain."

Analysis

Insight 1: The Principle of Defined Authority

Rambam explains that a private domain exists where a single authority controls the space. If the walls are not high enough, or if the space is not clearly demarcated, it reverts to a carmelit—an intermediate state where you lack true control. Decision Rule: If your strategic initiatives don't have "walls" (clear ownership, KPIs, and dedicated teams), they aren't private domains; they are carmelits. You cannot "carry" (transfer value) effectively in an ambiguous space. If you are managing your company’s core product development in a channel where everyone has input, you have no private domain. You must enclose your high-leverage projects so that they are "surrounded" by boundaries that keep the noise out.

Insight 2: The Verticality of Value

Rambam notes that a private domain extends "until the very heavens," while a public domain is limited to a height of ten handbreadths. Decision Rule: Your competitive advantage is a vertical asset. When you are in your "private domain" (your R&D, your proprietary data, your core culture), you aren't just limited by the ground-level competition. You have the freedom to build upward. When you are in the public domain (the market), you are constrained by the "ten handbreadths" of existing standards. Stop trying to compete in the "public domain" by acting like everyone else; move your innovation into your private domain, where your authority over the space allows for vertical scaling that the market cannot touch.

Insight 3: The Danger of the Intermediate State (Carmelit)

A carmelit is a place that isn't quite public, but isn't quite private. It’s a "widow" space—neither married to your strategy nor open to the public. Decision Rule: Most companies die in the carmelit. They aren't fully committed to their core competency (private), but they aren't fully integrated with the market (public). They are in an intermediate limbo. If a project or a product line cannot be clearly classified as a "private domain" (where you own the rules) or a "public domain" (where you are iterating based on market feedback), it is a carmelit. Kill the carmelit. Either harden the walls (make it a core, owned asset) or abandon it to the public domain.

Policy Move

Implement the "Ten Handbreadth" Zoning Policy. To prevent strategy drift, every major project must undergo a "Zoning Audit."

1. Define the Domain: Every project must be classified as Private (high-leverage, internal, protected, 4-wall ownership) or Public (outward-facing, market-reactive, feedback-heavy).
2. Hardening the Perimeter: Any project classified as Private must have a "10-handbreadth wall." This is defined as a specific, hard-coded KPI that cannot be changed by outside departments and a single, named authority who has final sign-off. If a project lacks this, it is officially designated a carmelit and receives zero headcount until it is properly "walled in."
3. Metric Proxy: Track "Context Switching Frequency." If an employee is forced to switch between Private work and Public work more than twice a day, they are effectively operating in a carmelit state, destroying the "private domain" efficiency. Target less than 20% of the day in this "intermediate" space.

Board-Level Question

"We are currently spending X% of our engineering and marketing energy on projects that are neither fully protected core assets nor fully exposed market-tested products. We are living in a carmelit. If we were to take our top three projects and force them to choose between becoming a 'Private Domain' (with absolute authority and clear, high walls) or a 'Public Domain' (with complete market exposure), which would we choose, and what 'walls' are we currently lacking to make those three projects true Private Domains?"

Takeaway

Strategy is not about what you do; it is about where you do it. If you don't build the walls, you don't own the domain. Stop trying to work in the carmelit. Either own the space completely or get out of it entirely. The "heavens" are only accessible from within your own private domain. Stop carrying your potential into the public square.