Unit Review: Practicing RO at Team Scale 2.3B.0-R

Key Structural Points

• Character (Arc 1) and method (Arc 2) give the team voluntary terms of cooperation and a correction discipline — but neither can enforce those terms structurally, encode recurring decisions into process, or detect the incentive failures that reward gaming over contribution.

• A team is the first scale at which cooperation becomes architecture rather than relationship — roles differentiate, information distributes unevenly, and informal arrangements harden into structures no one designed and no one audits.

• Sub-Arc 3B applies three RO design-pattern clusters at team scale: engineered and bounded interdependence (cooperation design and exit rights), encoded objective law and selective transparency (enforcement and disclosure), and systemic moral-hazard awareness (incentive detection and defusing).

• The reader carries named Arc 1 team tools (Trader Principle, payoff table, commitments contract, independence audit, feedback practices) and Arc 2 team tools (steelman-first protocol, error-friendly retro, practice audit, revision protocol) as operational prerequisites.

• Three units build the team structural practice: engineered and bounded interdependence (2.3B.1), team encoded objective law and selective transparency (2.3B.2), and team moral-hazard awareness (2.3B.3).

• The Team Evidence Pack (2.3B.3) assembles the sub-arc's artifacts — charter, entry and exit terms, payoff table, transparency matrix, dispute path, checklists, change logs, rotation schedule, and hazard scan — into a minimal, privacy-preserving packet following the principle: processes public by default, persons private by default.

• Phase I's stress test (1.3.9) identified two strain conditions directly relevant to team practice: politics under concentrated institutional failure (addressed in 2.3B.1's cooperation design and exit rights) and epistemology and ethics under adversarial pressure (addressed in 2.3B.2's enforcement and dispute mechanisms).

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)
• 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. One of RO's nine design patterns. (RO)
• evidence pack — A minimal, privacy-preserving collection of artifacts — private logs and public attestations — that proves practice without performative exposure. Assembled at each application level; synthesized in (2.3D.4). (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)
• privacy by design — The architectural commitment that persons remain selectively opaque to power; systems default to privacy and require justification for exposure, not the reverse. One of RO's nine design patterns. (RO)
• encoded objective law — The embedding of moral constraints into system design — through code or protocol, not merely law, habit, or virtue — so compliance is structural rather than dependent on individual virtue. One of RO's nine design patterns. (RO)
• selective transparency — The three-tier institutional disclosure discipline: processes and rules public by default, operational details auditable on request, personal information protected by design — the team-level expression of privacy by design and the asymmetry principle. (RO)
• systemic moral-hazard awareness — The design discipline of installing hazard detection as standard institutional practice. Its one WP4-grounded pattern is narrow: locating where a state-created shield has compelled a nonconsenting third party to underwrite a risk they never accepted. The broader hazard scan and counter-gaming toolkit this sub-arc uses are retained as an admitted-practice appendix — institutional management RO recommends because it works, not philosophy RO derives because rights require it. 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)

Concept Check

• Why does the article claim that a team is the first scale at which cooperation becomes architecture rather than relationship? What changes structurally when a group exceeds the capacity for direct personal observation?

• The article names specific Arc 1 and Arc 2 team tools the reader carries. Pick one tool from each arc and explain what structural gap remains that the tool cannot close — the gap that Sub-Arc 3B's design patterns address.

• Why does Sub-Arc 3B group engineered interdependence and bounded interdependence together as a single design-pattern cluster? What does each contribute that the other cannot, and why must they operate as a pair?

• The article describes three design-pattern clusters at team scale. What structural risk would a team face if it practiced the first cluster (cooperation design) but not the second (encoded objective law and selective transparency)?

• How does the Team Evidence Pack maintain the principle of processes public, persons private? Why would a team that publishes all its artifacts — including member performance data — be violating the design rather than exceeding it?

• The article claims that informal arrangements "harden into structures no one designed and no one audits." What specific tools from Sub-Arc 3B address this hardening, and at what point in the team's lifecycle should each be deployed?

• What would be missing from a team's practice if it completed Sub-Arc 3B but skipped Arc 1 and Arc 2?

Points to Ponder

• Think about a team you work with or have worked with recently. Could every member name the terms of their participation — what they contribute, what they receive, and how they could leave? If the terms are unclear, where did the ambiguity originate?

• Consider a metric your team uses to measure contribution or success. If that metric became the sole basis for recognition or compensation, how would rational members change their behavior? What would the Goodhart map reveal?

• The article argues that enforcement depending entirely on good faith has no structural defense when good faith fails. In your experience, what happened when a team's informal agreements encountered a genuine disagreement about obligations? Was the resolution structural or personal?

To Learn More

• Ostrom, Elinor. Governing the Commons: The Evolution of Institutions for Collective Action. Cambridge: Cambridge University Press, 1990. Demonstrates that cooperation can be self-governed through defined boundaries, proportional sanctions, and polycentric oversight — the empirical foundation for RO's engineered interdependence pattern applied to team-scale cooperation design in (2.3B.1).

• 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 RO's bounded interdependence pattern — the structural insight that participation is voluntary only when exit is practically exercisable, directly relevant to the team-level exit rights and portability terms in (2.3B.1).

• Kerr, Steven. "On the Folly of Rewarding A, While Hoping for B." Academy of Management Journal 18, no. 4 (1975): 769–783. The classic diagnostic of incentive misalignment — the structural condition where organizations reward behavior they wish to discourage while penalizing the behavior they desire — directly relevant to the Goodhart map and counter-gaming toolkit in (2.3B.3).