Mishnah Kinnim 2:1-2

Hook

You’re scaling, but your ops are messy. You have "unassigned" assets (capital, talent, inventory) moving between projects. When one resource gets "contaminated" or drifts, does it take down the whole batch? Founders often ignore "mixing" risk until the entire stack becomes invalid.

Text Snapshot

"If from an unassigned pair of birds a single pigeon flew... into the open air... it becomes invalid and it invalidates another bird as its counterpart... but if from the middle pair one bird flew to this side, and one bird flew to this side, then he has not lost anything." (Mishnah Kinnim 2:1-2)

Analysis

1. The Cost of Ambiguity

The Mishnah distinguishes between "unassigned" (setumah) and "assigned" resources. When assets are unassigned, they are fluid—but once a fluid asset drifts into a fixed-purpose system, it acts as a contagion. Decision Rule: Ambiguity is a liability. If you don't define the purpose of a resource before it enters the workflow, you risk invalidating the entire batch.

2. Contagion vs. Compensation

If a bird escapes into an "offering" group, it invalidates its pair. However, if it moves symmetrically (one to each side), it remains neutral. Decision Rule: If you must mix resources, do so symmetrically. Balanced exposure prevents systemic collapse.

3. The "Heir" Logic

The text notes that once an owner dies, the obligation for the Hatat (sin offering) survives, but the Olah (burnt offering) may not. Decision Rule: Prioritize legacy obligations. Some project debts are non-negotiable; others are tied to the founder’s presence. Know which is which.

Policy Move

Implement a "Tag-at-Entry" Protocol. No resource (capital, code branch, staff hour) enters a functional "production" state without a defined destination tag. If it isn't tagged, it is quarantined.

• KPI: Percentage of "Unassigned Resource Hours" (Goal: < 5%).

Board-Level Question

"We have several 'unassigned' projects currently bleeding into our core revenue streams. Which specific initiatives are we willing to mark as 'invalid' if these resources collide, and what is the cost of decoupling them today?"

Takeaway

Ambiguity is not flexibility; it is a ticking time bomb for your ROIC. Define it or lose it.