Unit Review: Engineered and Bounded Interdependence 2.3B.1-R

Key Structural Points

• Cooperation that is not explicitly designed becomes implicitly coercive — roles accrete informally, decision rights are assumed, and exit costs accumulate invisibly until participation is voluntary in name only.

• Engineered interdependence at team scale requires publishing the terms of cooperation: role map, decision rights matrix, interface specifications, consent validity checkpoints, and review date — in a team charter that every member can read, contest, and verify.

• Bounded interdependence at team scale requires defining the terms to join, stay, and leave — entry criteria, performance expectations, and clean exit with handoff protocol, data portability, and reputation protection.

• Consent validity requires four structural conditions: capacity (the member understands the terms), information (the member has access to standards and decision rights), absence of coercion (the member can exit without losing portable work), and recourse (the member has meaningful remedies if terms are violated). Any missing condition makes the consent structurally invalid.

• Dependency power — the structural capacity to impose costs on another party's departure — is the force that bounded interdependence limits. Clean exit terms bound that power so that cooperation remains voluntary throughout, not merely at the moment of entry.

• The interface map makes team dependencies visible — which roles are single points of failure, which interfaces are fragile, where backup capacity is needed — and connects to Phase I's strain condition on politics under concentrated institutional failure (1.3.9).

• Payoff alignment gives the Trader Principle (2.1.4) structural enforcement through a payoff table that maps contributions to outcomes, making recognition and compensation visible and defensible rather than opaque and arbitrary.

• The participation test integrates the unit's structural argument into four diagnostic questions: can each member know the terms, contest them, exit if unsatisfied, and take portable work? Each missing element identifies where coercive structure hides inside voluntary language.

• The restraint principle (2.3B.1-3) bounds the charter itself — limiting structural enforcement to decisions that genuinely require it and trusting trained judgment for everything else, so that governance remains lean rather than bureaucratic.

Philosophical Lexicon

• bounded interdependence — Resilient Objectivism's design discipline governing two structurally distinct domains: for voluntary cooperative arrangements, a design recommendation — clean exit, meaningful recourse, and data portability — grounded in the builder's own self-interest, not an entitlement owed to a departing participant; for the exercise of public force, a categorical requirement that legitimate authority stay bounded to retaliatory force against initiators. One of RO's nine design patterns. (RO)
• consent theater — Mechanisms that present the appearance of consent without satisfying the structural conditions for genuine consent — capacity, information, absence of coercion, and recourse. (RO)
• dependency power — The structural capacity of one party to impose costs on another's exit or non-compliance. High dependency power degrades a cooperation model's own voluntariness; bounded interdependence limits it. (RO)
• engineered interdependence — The design of cooperation so that its coordination mechanism cannot become standing authority over the participants — value created jointly, incentives supporting the value produced, reciprocal commitments made credible, without turning coordination into control. Part of its moral posture is inherited from Kelley's benevolence — an unproven counterparty can rationally be treated as a potential source of value rather than a presumptive threat; structure supports that posture but does not manufacture it. One of RO's nine design patterns. (RO)
• participation constraint — The continuous requirement that every participant in a cooperative framework is better off inside than outside — a floor that must be maintained throughout participation, not merely satisfied at entry. (RO)
• the restraint principle — An architectural extension that limits how much authority, coupling, complexity, and blast radius a system's safeguards may claim — does the design keep failure local, make authority legible, and avoid creating a general power to solve a narrow problem? One of RO's nine design patterns. (RO)
• Trader Principle — The principle that human relationships should be exchanges of value — where each party contributes something the other values and receives something in return, with no sacrifice on either side. (TO)

Unit Glossary

• clean exit — An exit structure that specifies handoff protocol, data portability, reference process, and legal boundaries (non-compete and IP), so that departure does not require forfeiting portable work or reputation.
• consent validity checkpoint — A structured assessment of whether each team member can understand the terms (capacity), access needed information, exit without losing portable work (absence of coercion), and obtain meaningful remedies if terms are violated (recourse).
• decision rights matrix — A table mapping each major decision type to its decider, consulted parties, advisors, informed parties, timeline, and appeal process.
• entry criteria — Published standards specifying what knowledge a new member must bring, what the team teaches during onboarding, and what learning goals apply within the first month.
• interface map — A visual representation of team dependencies showing which roles depend on which, for what, and what happens if the dependency breaks — used to identify structural fragility.
• interface specification — A contract between two roles specifying what is delivered, the quality standard, timing, recourse if defective, and who maintains the specification.
• participation test — Four diagnostic questions assessing whether each team member can know the terms, contest them, exit if unsatisfied, and take portable work — each missing element identifying coercive structure.
• payoff table — A mapping of each role's contributions to team outcomes and the recognition, compensation, and advancement that track actual value creation.
• performance expectations — Published, testable standards for what each role produces, how it is measured, the feedback cycle, and the recourse if performance falls below standard.
• role map — A specification of each role's scope of authority — what the role decides, what it does not decide, and who it coordinates with.
• team charter — A document specifying role map, decision rights matrix, interface specifications, consent validity checkpoints, and review date — the structural terms of team cooperation.

Concept Check

• Why does the article claim that consent valid at entry but never re-examined degrades over time? What specific structural changes could make initially valid consent structurally invalid?

• The consent validity checkpoint has four conditions. Explain why absence of coercion and recourse are distinct requirements — what structural condition would satisfy one but fail the other?

• How does the interface map connect to Phase I's strain condition on politics under concentrated institutional failure (1.3.9)? What does a team-level dependency concentration share with the institutional-level load case?

• The article distinguishes the payoff table from equal pay. What structural condition does payoff alignment require that equal pay does not — and why is the distinction morally relevant under the Trader Principle?

• The participation test asks four questions. A team runs the test and finds that every member can know the terms and contest them, but two members cannot exit without losing portable work. What specific structural repair would address this — and which toolkit in the unit provides it?

• Why does the restraint sidebar (2.3B.1-3) argue that starting minimal and expanding on evidence produces a better charter than anticipating every need? What governance cost does anticipatory structure impose?

• What structural function does the review date serve in the team charter? How does a charter without a review date compare to a policy without a sunset clause (2.2.5)?

• What would be missing from a team's cooperation design if it built the charter but not the entry, exit, and portability terms? Which of the four consent validity conditions would fail?

• How does the decision rights matrix prevent the condition where two people each believe they hold the same decision right? What happens to the team when that ambiguity is not resolved?

Points to Ponder

• Think about a team you work with or have worked with. Could you name the actual decision rights — who decides hiring, budget, technical direction, process changes? If the rights are informal, what happens when two people claim the same authority?

• Consider your own exit terms. If you decided to leave your current team or organization tomorrow, what would you take with you? What would you lose? Were those terms published before you joined — or did you discover them only now, reading this question?

• The article argues that payoff alignment does not require mathematical precision — it requires visibility and defensibility. In your experience, is the gap between stated values ("we reward merit") and actual practice (compensation tracks negotiation skill or seniority) visible to the people affected? What would change if it were?

• The restraint sidebar argues that a charter should be as small as it can be while still making cooperation genuinely voluntary. Think about a governance structure you have encountered — a handbook, a set of team rules, a compliance framework. How much of it was load-bearing, and how much was decorative?

To Learn More

• Ostrom, Elinor. Governing the Commons: The Evolution of Institutions for Collective Action. Cambridge: Cambridge University Press, 1990. Provides the empirical foundation for the claim that cooperation can be self-governed through defined boundaries, proportional sanctions, and polycentric oversight — the principles that RO's engineered interdependence draws upon for team-scale cooperation design.

• Hirschman, Albert O. Exit, Voice, and Loyalty: Responses to Decline in Firms, Organizations, and States. Cambridge, MA: Harvard University Press, 1970. Introduces the exit-voice framework that grounds bounded interdependence — the structural insight that participation is voluntary only when exit is practically exercisable, directly relevant to the participation test and the clean exit structures in this unit.

• Williamson, Oliver E. The Economic Institutions of Capitalism: Firms, Markets, Relational Contracting. New York: Free Press, 1985. Develops the transaction cost framework that explains why cooperation structures accumulate dependency power — asset specificity, bounded rationality, and opportunism create the conditions that the team charter and exit terms are designed to make visible and contestable.