Mishneh Torah, Tithes 4-6

Hook

Founders often struggle with the "threshold of obligation." When does a casual experiment become a formal business? When does a side-hustle become a taxable entity? The Rambam clarifies that obligations are triggered by intent and permanence—not just by the mere presence of an asset.

Text Snapshot

"The obligation to tithe is not established... until one brings it into his home... provided he brings the produce in through the gate... If, however, he brought produce in from the roof or from the yard, he is exempt." Mishneh Torah, Tithes 4:1

Analysis

Insight 1: The "Front Door" Rule

The law distinguishes between bringing assets in through the "gate" (the intended, formal path) versus the "roof" or "yard" (an informal, accidental, or bypass route). In business, this is the difference between a deliberate product launch and a "shadow IT" project. If you aren't bringing your operations through the formal gate of your organization’s infrastructure, you are dodging the governance that ensures stability.

Insight 2: Context Defines the Asset

A structure like a summer shelter or a guardhouse doesn’t establish an obligation for everyone, but it does for the owner Mishneh Torah, Tithes 4:6. Your processes aren't universal; they are defined by your specific role. If you are the founder, you have "residency" in your company’s infrastructure—what is a casual snack for a visitor is a formal obligation for you.

Insight 3: Permanent vs. Temporary

Structures lacking permanence, like temporary booths or leantos, don't trigger the obligation Mishneh Torah, Tithes 4:5. Don't over-engineer governance for temporary "MVP" phases, but recognize that as soon as you move into a "permanent dwelling" (a scalable, repeatable process), the ethical and legal weight of that asset increases.

Policy Move

The "Formalization Trigger" Policy: Create a clear internal threshold for when a project transitions from "R&D/Experiment" (exempt) to "Production" (obligated). Use a single KPI: User-Dependency Ratio. If more than 10% of the company's daily workflow relies on an un-governed tool or process, it must be "brought through the gate" (documented, audited, and secured).

Board-Level Question

"Are we currently operating any of our core business functions 'through the roof'—bypassing our formal systems—and what liability does that create when these 'temporary' workarounds become our permanent reality?"

Takeaway

Governance isn't an arbitrary burden; it is the recognition that when you move an asset into your "home" (your core business infrastructure), you have reached a level of maturity that demands accountability. Don't hide from the gate.