Mishneh Torah, Marriage 8

Hook

You’re closing a partnership or hiring a key lead. You think you’ve aligned on the "vibe," but you never explicitly defined the criteria. You’re building on sand. If the contract doesn't match the reality, the deal is null.

Text Snapshot

"In all these and in any similar instance, the woman is not consecrated... [The rationale is that] feelings in one's heart are not [the same as explicit] statements" Mishneh Torah, Marriage 8:2.

Analysis

1. The "Mind Reading" Trap

Founders often assume shared intent. The text teaches that an unstated assumption—even a strong one—is functionally zero. If you don't define the "dinar of gold" vs. "dinar of silver," you haven't made a deal; you've made a misunderstanding.

2. The Power of Explicit Stipulation

Specificity is an act of respect. By stating, "I want someone who knows how to read [the Torah]" Mishneh Torah, Marriage 8:4, the parties define the threshold for success. Ambiguity is the enemy of binding commitments.

3. Subjectivity vs. Objective Standard

The text notes that "feelings in one's heart are not [the same as explicit] statements" Mishneh Torah, Marriage 8:2. You cannot pivot to "I felt like he was a founder" when the equity grant was contingent on "revenue growth."

Policy Move

The "Explicit Conditions" Audit: Before finalizing any high-stakes agreement (hiring, M&A, co-founder vesting), implement a "Definition of Success" document. If it isn't explicitly listed in the term sheet/contract, it is not a condition of the deal.

Board-Level Question

"Are we relying on 'implied culture' to drive performance, or have we explicitly documented the specific, measurable outcomes that define our success?"

Takeaway

Stop hiring and partnering on "vibes." If the condition isn't stated, the commitment isn't real. Document the delta between what you expect and what you stipulated.

KPI Proxy: % of contract disputes caused by "implied" expectations vs. explicit clauses.