Unit Review: Polycentric Governance and Exit Rights 2.3D.1-R

Key Structural Points

• Enterprise-scale governance that concentrates authority in a single point will eventually be captured by it — not because initial stewards lack virtue, but because institutional design that permits capture creates incentive paths that erode virtue over time. Phase I's strain condition on politics under concentrated institutional failure (1.3.9) names this load case.

• Polycentric governance distributes authority across overlapping jurisdictions, each with defined limits, transparent authority maps, and explicit escalation paths. Intentional overlap creates friction that prevents unilateral decision-making and makes capture paths visible. The design principle: no single failure — institutional, political, or technological — should compromise the entire governance structure.

• The enterprise governance charter names four structural questions: who decides what, by what logic each authority is constrained, what happens when authorities conflict, and what makes a decision reviewable and renewable. The charter extends the organizational institutional charter (2.3C.1) to multi-organizational governance.

• Jurisdiction maps visualize who decides what, where overlapping authorities create redundancy, and what mechanisms resolve conflicts. The map is both diagnostic (audit of current governance) and prescriptive (design tool for future governance). Three failure patterns — phantom overlaps, cascade authority, and hidden authority — indicate that the map has drifted from genuine polycentric governance.

• Capture pathways are predictable sequences through which governance shifts from serving participants to serving entrenched authority. Common examples: information asymmetry leading to gradual redefinition of oversight boundaries, board insularity leading to closed-club governance, audit dependence on executive leadership leading to compliance theater. Polycentric design multiplies the conspiracies required to capture the enterprise.

• Exit rights test whether participants are genuinely interdependent (locked in by choice) or captured (locked in by circumstance). The four-part test: can you leave, take your data, verify the terms, and migrate without prohibitive cost? All four must be substantially met for exit to be genuine rather than ceremonial.

• Bounded interdependence's voluntary-arrangements branch (1.2.6) recommends exit as a first-class capability — data portability, custody models (self-custody, escrow, multi-signature), interoperability specifications, and verifiable exit costs — grounded in the enterprise's own interest in an arrangement worth staying in, not an entitlement owed to a departing participant. Exit requires engineering attention, not afterthought.

• The staged-judgment lifecycle (hypothesis → scoped finding → decision recommendation → binding rule) constrains how governance claims acquire coercive force across jurisdictions. Each stage requires restraint mechanisms (published rationale, contestability) and exit mechanisms (appeals, sunsets, independent adjudication). No claim may acquire coercive force without a defined appeals pathway.

• Exit costs must be transparent and proportionate to participant stake. If exit costs exceed a participant's annual benefit, exit is economically irrational — the participant is locked in regardless of contractual language. The enterprise measures, publishes, and targets exit cost reduction.

• The unit ships three governance artifacts: the enterprise governance charter (naming authorities, constraints, overlaps, adjudication logic, and decision review cycles), the jurisdiction map (showing decision domains and capture-resistance architecture), and the exit rights checklist (honest assessment of whether exit is genuine). Maintenance cadence: governance review quarterly, charter review annually, stress test with stakeholders every two years.

Philosophical Lexicon

• answerability — The design discipline of keeping responsibility locatable inside institutions: every consequential choice inside a structure was made by some person, and a structure that obscures which person chose what does not relieve anyone of responsibility — it makes responsibility unlocatable. One of RO's nine design patterns. (RO)
• bounded interdependence — Two structurally distinct domains: for voluntary cooperative arrangements, a design recommendation — clean exit, meaningful recourse, 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 moral requirement that legitimate authority be bounded to retaliatory use against those who initiated it. One of RO's nine design patterns. (RO)
• the restraint principle — The structural commitment to limiting scope, surface area, and coupling so that failure stays local and reversible. One of RO's nine design patterns. (RO)
• polycentric governance — A decentralized system of overlapping, semi-autonomous institutions that share responsibility and feedback, drawn from Elinor Ostrom's institutional analysis; the governance model that replaces both centralized control and unstructured libertarian minimalism. At enterprise scale, operationalized through jurisdiction maps and the design principle that no single failure should compromise the entire governance structure. (RO)
• capture pathway — The four-stage degradation mechanism — incentive misalignment, normalization, oversight accommodation, structural capture — by which undetected moral hazard converts institutional architecture into extraction infrastructure. Examples at enterprise scale: information asymmetry leading to gradual redefinition of oversight boundaries; executive control of hiring leading to loyalty capture; audit dependence on executive budget leading to compliance theater. (RO)
• exit rights — The design recommendation — prudentially grounded in the builder's own self-interest, not an entitlement owed to a departing participant — that a cooperative arrangement provide departure under four conditions: unconditional availability, non-forfeiture, non-retaliation, and bounded cost. At enterprise scale, operationalized through data portability, custody models, interoperability specifications, and verifiable exit costs. (RO)
• consent theater — The performance of participant consent without its structural reality. Exit rights that exist on paper but cannot be exercised; governance consultation that gathers input but never changes decisions; transparency that publishes data no one can verify. (RO)

Unit Glossary

• jurisdiction map — A visual artifact showing decision domains, overlapping authorities, constraints, and review cycles within a polycentric governance system. Distinguished from an organizational chart (which shows reporting lines, not decision domains).
• phantom overlap — A jurisdiction shown on the governance map as overlapping with others, but in practice only one jurisdiction decides and others rubber-stamp. Gives the appearance of polycentric governance without its substance.
• cascade authority — A governance structure that appears polycentric but functions as a hierarchy, with authority flowing downward through a single chain. The diagnostic: can a lower authority block a higher authority's decision?
• hidden authority — Real decision-making power that operates informally — through executive lunches, founder veto, or unwritten agreements — while formal governance structures exist as theater.
• custody model — Who holds the actual assets (keys, credentials, ledgers, records) the enterprise manages on behalf of participants. Three models: self-custody (participant holds), escrow (neutral third party), multi-signature (both hold).
• interoperability specification — Open, auditable, enterprise-neutral standards for how systems communicate. Enables switching between alternatives without rebuilding from scratch.

Concept Check

• Polycentric governance intentionally creates friction through overlapping jurisdictions. Why is friction a feature rather than a defect? What structural risk does the enterprise accept by tolerating slower decisions — and what greater risk does it avoid?

• The four-part exit rights test includes "can you verify the terms?" Why is independent verification necessary for bounded interdependence, given that the enterprise might have an excellent track record?

• Exit costs that are prohibitive relative to participant stake create lock-in regardless of contractual language. How would you determine whether exit costs are prohibitive for a specific participant — and why does the answer depend on the participant's stake rather than a fixed dollar amount?

• The staged-judgment lifecycle (hypothesis → finding → recommendation → binding rule) includes restraint and exit mechanisms at each stage. What is the purpose of restraint at Stage 1 (hypothesis), before any coercive force has been applied?

• The article claims that polycentric design "multiplies the conspiracies required" to capture an enterprise. What structural feature of polycentric governance creates this multiplication — and under what conditions might it fail?

• The enterprise governance charter extends the organizational institutional charter (2.3C.1) to multi-organizational governance. What structural challenge does the multi-organizational context introduce that a single-organization charter does not face?

• What would be missing from an enterprise's governance if it completed a polycentric jurisdiction map but did not implement exit rights? Why are both required?

• Phase I's strain condition on politics under concentrated institutional failure (1.3.9) names the load case this unit answers. What distinguishes an enterprise that has genuinely addressed that strain condition from one that has merely drawn a jurisdiction map without changing where authority actually sits?

• A jurisdiction map can drift from genuine polycentric governance through phantom overlap, cascade authority, or hidden authority. Pick one of the three and explain what evidence would distinguish it from a jurisdiction map that is functioning as designed.

• The unit ships three governance artifacts on a maintenance cadence (governance review quarterly, charter review annually, stress test every two years). What would an enterprise's practice look like if it produced all three artifacts once but never revisited the cadence — and why does the article treat that as a distinct failure from never producing them at all?

Points to Ponder

• Think about a multi-organizational system you participate in — an industry standard, a regulatory framework, a supply chain, or a professional certification body. Can you identify where authority is concentrated? Is there a single point whose capture would compromise the system's integrity?

• Consider the exit conditions of that system. If you or your organization wanted to leave, what would it cost? Is the cost structural (data lock-in, proprietary formats, contractual penalties) or reputational? What would need to change for exit to be genuinely exercisable?

• The hardest question: if someone tried to exit your enterprise right now, how would you actually know whether they could do it easily? Would you design a test and run it?

To Learn More

• Ostrom, Elinor. Governing the Commons: The Evolution of Institutions for Collective Action. Cambridge: Cambridge University Press, 1990. Foundational work on polycentric governance in resource management. Demonstrates how overlapping authorities with defined rules and graduated sanctions create robustness that single-point authority cannot. Directly relevant to (2.3D.1)'s jurisdiction map and the structural argument for distributed authority.

• Hirschman, Albert O. Exit, Voice, and Loyalty: Responses to Decline in Firms, Organizations, and States. Cambridge: Harvard University Press, 1970. Classic framework showing how exit and voice function as complementary mechanisms for organizational discipline. Exit without voice produces silent departure with no feedback. Voice without exit produces capture — participants can complain but not leave. The framework grounds (2.3D.1)'s argument that exit rights and governance participation are structurally inseparable.

• Lessig, Lawrence. Code: And Other Laws of Cyberspace. Version 2.0. New York: Basic Books, 2006. Develops the thesis that system architecture constrains behavior more effectively than legal rules alone. Directly relevant to the argument that governance restraint must be encoded into structure, not delegated to the virtue of the people who operate it.