Chullin 104

Hook

Founders often agonize over the "scope creep" of their promises. You vow to prioritize customer success, but does that include every edge-case feature request? You commit to a pivot, but does it cover the legacy product line? In business, your "vow" is only as good as the market’s common understanding of your language.

Text Snapshot

Chullin 104a discusses the parameters of a vow: "One who takes a vow that meat is prohibited to him is permitted to eat the meat of fish and grasshoppers." The Gemara probes why certain items fall in or out of the category, noting that "anything about which an agent... would inquire... is considered its type."

Analysis: The Logic of Scope

1. The Agent Test

Rabbi Akiva argues that if an agent sent to buy "vegetables" asks if they should purchase "gourds," it proves that gourds are within the semantic scope of "vegetables." If they didn't fall under the category, the agent wouldn't ask; they would just omit them. Decision Rule: If your product or policy requires constant clarification from your team, it is effectively part of the core category. Stop pretending it’s an exception.

2. The "Day of Bleeding" Leniency

The commentators (Tosafot) note that fish are only permitted to a person who vowed against "meat" because, on days when one is "ill" or receiving medical treatment (like bloodletting), people do not eat fish. Decision Rule: Your market’s behavior is defined by their "normal" state, not their edge cases. Don't build your core strategy around the behavior of someone who is "sick" or operating in a crisis.

3. Precision vs. Intent

The Gemara highlights that while the law seeks precision, it must respect the loshon bnei adam (common human language). Decision Rule: If you define your mission too broadly, you’ll be trapped by the unintended consequences of your own vague vocabulary.

Policy Move

The "Definition Audit": Every quarter, review your top 3 customer-facing commitments (SLAs, mission statements, roadmap promises). If your support team has to explain what you meant by a term more than 5% of the time, delete the term and replace it with a specific binary: "We do X, we do not do Y."

Board-Level Question

"Are we currently suffering from 'scope creep' because we’ve allowed our internal definitions of success to diverge from our customer's common-sense understanding?"

Takeaway

Don't let your business promises become a trap of your own making. If you want the freedom to act, define your boundaries with the precision of a contract, not the sentiment of a marketing slogan.

Metric: Percentage of support tickets generated by ambiguity in core policy documents.