Practicing RO at Team Scale 2.3B.0

What You Carry Into Team Structure

The reader who arrives here has already built two layers of team practice and one layer of individual structural discipline.

Arc 1 installed the character at team scale. The Trader Principle became the moral baseline for voluntary cooperation — defined contributions, defined returns, defined exit (2.1.4). Independence became a practiced discipline inside the group: the independence audit tracking whether position changes were driven by evidence or social pressure, the structural habit of stating your actual assessment even when the group has moved on (2.1.5). Justice in recognition became structural through the payoff table mapping contributions to outcomes, and honesty in feedback became operational through the work-focused, evidence-based standard that replaces polite evasion with direct assessment. The Traditional Objectivism (TO) team practice is a working cooperation system: voluntary, transparent, and grounded in individual judgment.

Arc 2 layered in the method. Disagreement as data converted conflict into upgrade path — the steelman-first protocol requiring the team to reconstruct a dissenting view before evaluating it, the error-friendly retro installing required dissent through four diagnostic questions (2.2.3). Method over canon prevented team norms from calcifying — the practice audit asking whether each norm still solves the problem it was created for, the revision protocol requiring safe proposal, evidence-based evaluation, known decision mechanism, and tracked implementation (2.2.4). The Open Objectivism (OO) team practice keeps cooperation honest: it adds the correction mechanisms that prevent agreement from hardening into conformity and norms from fossilizing into identity.

Character and method at team scale are genuine achievements. The Trader Principle works. Disagreement as data works. But neither can enforce the terms of cooperation when a member's exit is practically blocked by switching costs the team did not design but the team's structure silently accumulated. Neither can encode recurring decision constraints into the team's process so that compliance does not depend on every member's vigilance at every moment. Neither can detect the incentive structures that reward gaming over contribution — the quiet drift from measuring value to measuring the appearance of value. Those are structural problems. They require structural tools.

Why Structure Matters Here

A team is the first scale at which cooperation becomes architecture rather than relationship. Two people cooperating can rely on mutual knowledge and direct observation. A team of five or fifteen cannot. Roles differentiate. Information distributes unevenly. Decisions compound. And the informal arrangements that served the original group quietly harden into structures that no one designed and no one audits.

This is the structural gap that Resilient Objectivism (RO) was built to close. Phase I constructed nine design patterns — structural tools designed to hold where character and method alone cannot. Sub-Arc 3B applies three pattern clusters at team scale: engineered interdependence (1.2.5) and bounded interdependence (1.2.6) as the design framework for cooperation that remains genuinely voluntary; encoded objective law (1.2.2) and selective transparency — the team-level expression of privacy by design (1.2.4) and the asymmetry principle — as the enforcement and disclosure disciplines that keep team processes honest while protecting persons; and systemic moral-hazard awareness (1.2.8) as the detection mechanism for incentive structures that reward gaming over contribution.

The clustering follows the logic of team cooperation itself. Before you can enforce team agreements or scan for hazards, you need agreements worth enforcing — a charter that names roles, rights, obligations, and the terms for joining, staying, and leaving. Before you can detect gaming, you need metrics tied to actual value creation rather than proxy signals. And before any of it holds, you need the structural guarantee that participation remains voluntary: clean exit, portable standing, and recourse that does not route through the party being challenged.

Sub-Arc 3A established that structural competence scales upward from the individual. Sub-Arc 3B tests that claim. An individual who can verify claims, manage keys, and limit exposure is structurally literate. A team that can charter its cooperation, enforce its agreements without depending on every member's constant virtue, detect its own incentive failures, and prove its practice without exposing its members — that team has made the structural tools operational at the first scale where cooperation becomes architecture.

What Sub-Arc 3B Teaches

Three units build the team structural practice. Each ships a toolkit. Each connects to the TO character and OO method the reader already carries — and each adds the structural enforcement that makes both hold under the operational pressures that character and method alone cannot govern.

(2.3B.1) Engineered and Bounded Interdependence. The first unit applies two of RO's design patterns — engineered interdependence and bounded interdependence — as the design framework for team cooperation. The Team Charter names each role's scope, decision rights, obligations, and interfaces, with consent validity checks and a review date. Entry requirements, performance expectations, and clean exit terms — handoff, knowledge transfer, data portability — are published alongside the charter, not discovered during conflict. The interface map shows who depends on whom, for what, and what happens if one party exits. Payoff alignment — the structural enforcement of Arc 1's Trader Principle — gets a payoff table mapping contributions to outcomes. The participation test closes the unit: can a member know the terms, contest them, exit if unsatisfied, and take their portable work with them? Each missing element identifies coercive structure hiding inside voluntary language. Phase I's strain condition on politics under concentrated institutional failure (1.3.9) is directly relevant: cooperation structures that concentrate dependency without visibility are the team-scale version of the load case.

(2.3B.2) Team Encoded Objective Law and Selective Transparency. The second unit applies encoded objective law (1.2.2) and privacy by design (1.2.4) as team-level enforcement and disclosure disciplines. Encoded objective law at this scale means turning recurring decisions into short checklists, requiring signatures for key actions, and keeping an append-only log of material changes. The Enforce-in-Code decision tree asks whether a decision's stakes warrant structural enforcement or whether trained judgment suffices. Selective transparency — processes public, persons private — gets a transparency matrix specifying exactly what is visible, what is protected, and why. Rotation and review mechanisms install anti-capture and anti-clique disciplines. The dispute path provides fast, fair, auditable resolution: informal resolution through mediated review through written decision through appeal. Phase I's strain condition on epistemology and ethics under adversarial pressure applies here: a team whose enforcement depends entirely on good faith has no structural defense when good faith fails.

(2.3B.3) Team Moral-Hazard Awareness. The third unit applies systemic moral-hazard awareness (1.2.8) as the team's detection and defusing discipline. The Goodhart map identifies metrics that invite gaming and installs counter-gaming patterns: metric rotation, audit-on-exception, and clawbacks for bonuses tied to bad signals. Capture resistance asks the structural test: if the most powerful member left tomorrow, would the team's accountability mechanisms still function? The counter-gaming toolkit is a small library of defensive patterns drawn from Phase I's construction. The Team Evidence Pack closes the sub-arc: charter, entry and exit terms, payoff table, transparency matrix, dispute path, checklists, change logs, rotation schedule, and hazard scan — bundled into a minimal, privacy-preserving packet that proves the team's practice is real. The evidence-pack design follows the principle that runs through all of Arc 3: processes public by default; persons private by default.

The reader who completes Sub-Arc 3B carries a structural team practice layered on top of TO's character and OO's method. They can charter cooperation, enforce agreements, detect incentive failures, resolve disputes, and prove all of it — without exposing the persons who make the team work. What they cannot yet do is make these disciplines hold across an organization, where the structures are larger, the power asymmetries are deeper, and the consequences of failure propagate further. That is Sub-Arc 3C's work.