Cross-Unit Governance Instruments

docs/03-governance/00-overview.md states that the Adaptive Governance Framework (AGF) — the network’s layered governance system — distributes decision-making across United Micro Enterprises (UMEs) — small, self-managing venture teams of up to ~15 people — Strategic Enterprise Partnerships (SEPs) — joint ventures between teams — “and ecosystem layers such as the MEE,” and names “Responsive” among the AGF’s stated properties: the system “adapts to new challenges through versioning, soft-forking, and governance-layer experimentation.” Neither passage names an instrument for coordinating between governing units that fall short of forming a SEP, for settling a dispute between units whose jurisdiction overlaps, or for running the versioning and experimentation the “Responsive” property names. docs/02-structure/03-strategic-enterprise-partnerships.md and docs/11-deployment/04-sep-structuring.md §11.4.3 already specify a SEP Charter — a jointly signed governing document for a new joint-venture entity that UMEs form together, with its own decision protocol, conflict protocols, and exit provisions. This section describes three further instruments that do not require forming a new entity: a standing coordinating role between units, an agreement format for cross-boundary matters, and a bounded space for testing a governance change before it is adopted network-wide.

Source and provenance. The material below is drawn from the staged extraction’s ## Countermeasures section, ultimately sourced to ~/code/papr/polycentric-governance/005-r-claude.md and ~/code/papr/polycentric-governance/005-r-gemini.md — two of four model-generated responses to a prompt asking for solutions to the gaps that docs/09-adversarial-analysis/05-polycentric-failure-modes.md catalogs as the network’s inherited polycentric failure modes. The extraction’s own assessment, carried forward unchanged in docs/09-adversarial-analysis/06-countermeasures-and-detection.md §9.6.20, is that this pass “largely reproduces general public-administration content rather than mechanisms specific to this model,” and that four independent model variants converged on similar answers to a prompt that asked for novel solutions. No claim is made in this section that any named study, author, or research tradition established these three instruments: the sources are model-generated responses citing no author or paper, on the same footing as the failure-mode material in §9.5 of chapter 09. What follows states what the source proposes, not a finding independently verified against public-administration scholarship.

Each instrument below is one the extraction and docs/09-adversarial-analysis/06-countermeasures-and-detection.md §9.6.20 map to specific polycentric failure modes that docs/09-adversarial-analysis/05-polycentric-failure-modes.md catalogs by name; those entries are cited by name and section below and are not restated here.

A. Bridging Organizations

The source describes a bridging organization as a standing coordinating role rather than a joint venture: “a network of organizations specifically designed to facilitate coordination/communication/collaboration among governing units, developing shared goals/strategies/metrics and a platform for joint problem-solving and resource-sharing.” As stated, the role is ongoing and cross-cutting — it exists to coordinate between units on a continuing basis, not to jointly own or operate a specific venture, which is what a SEP does. The source states no composition, no appointment process, and no scope limit for a bridging organization; whether one bridging organization serves the whole network or several serve different clusters of units is not addressed.

The AGF already provides a coordinating layer above UMEs and SEPs (docs/03-governance/00-overview.md), and docs/11-deployment/04-sep-structuring.md §11.4.3 names an existing reviewing role — “the HAO Coordination Node, or an equivalent integrator (e.g., provide.io)” — that reviews a SEP Charter for alignment and risk at formation. Neither of those is stated by any source as performing the standing, cross-unit coordinating function described here; a bridging organization, as the source states it, is a distinct institutional role, not a restatement of either.

This instrument is the one the extraction and §9.6.20 map to the coordination cluster that docs/09-adversarial-analysis/05-polycentric-failure-modes.md divides between Absence of Overarching Vision (§9.5.1) and Cross-Boundary Problem Paralysis (§9.5.2); those entries are not restated here.

Source: 005-r-claude.md.

B. Joint Governance Agreements

The source describes a joint governance agreement as a formal agreement between governing units for a cross-boundary matter, without requiring that the units form a new joint entity to hold it: “formal agreements outlining shared responsibilities, commitments, and accountability mechanisms for cross-boundary issues, including joint decision-making, cost-sharing, dispute resolution provisions.” Three components are named directly in that sentence: a joint decision-making provision, a cost-sharing provision, and a dispute-resolution provision. The source states no template for any of the three, no minimum content, and no body that reviews or ratifies an agreement before it takes effect.

A SEP Charter, as docs/11-deployment/04-sep-structuring.md §11.4.3 specifies it, already covers cost allocation, decision protocol, and conflict protocols for UMEs that form a joint venture together. The source for this instrument does not state whether a joint governance agreement is meant for units that have not formed a SEP, for a matter narrower than a full joint venture would warrant, or for a relationship between a unit and a layer of the AGF above it rather than between two UMEs; the relationship between the two instruments is not addressed by any source, and this section states that gap rather than resolving it.

This instrument is the one the extraction and §9.6.20 map to the jurisdictional-overlap cluster that docs/09-adversarial-analysis/05-polycentric-failure-modes.md catalogs as Conflict Deadlock (§9.5.7), and it bears on Cross-Boundary Problem Paralysis (§9.5.2) through the cross-boundary responsibilities it records; those entries are not restated here.

Source: 005-r-claude.md.

C. Governance Sandboxes with Sunset Clauses

Two sources name closely related versions of this instrument. 005-r-claude.md names “policy labs” and “governance sandboxes” as “designated zones where governing units test innovative approaches to complex problems in a controlled setting, piloting new technologies/models/partnerships and generating evidence for broader system change,” and pairs the sandbox form explicitly with “adaptive regulation and sunset clauses,” stated as enabling “time-limited rule testing with built-in monitoring/evaluation/adjustment.” 005-r-gemini.md independently names “‘Sunset Clauses’ for Policies” as a standalone instrument. As stated across the two sources, the instrument combines a bounded space for testing a governance change with a clause that ends the test automatically unless a further decision extends or adopts it. Neither source states how long a sandbox runs by default, what evidence standard determines whether a tested change is adopted network-wide, or which body authorizes a sandbox in the first place.

docs/03-governance/00-overview.md already names “versioning, soft-forking, and governance-layer experimentation” as how the AGF’s “Responsive” property operates, without naming an instrument for it; a governance sandbox with a sunset clause is one way of giving that stated property a concrete form, though no source states that connection, and this section does not adopt it as more than a plausible reading of the two passages together.

This instrument is the one the extraction and §9.6.20 map to the entrenchment and path-dependence cluster that docs/09-adversarial-analysis/05-polycentric-failure-modes.md folds into Absence of Overarching Vision (§9.5.1); that entry is not restated here.

Sources: 005-r-claude.md, 005-r-gemini.md.

Instruments not covered here. The same Countermeasures material records four further instruments that docs/09-adversarial-analysis/06-countermeasures-and-detection.md §9.6.20 also maps to chapter 03: equity scorecards paired with redistributive transfers, citizen audits with open-data tracking, resilience networks, and social impact bonds for governance. It also maps knowledge-sharing platforms and adaptive, participatory monitoring and evaluation to this chapter, which are likewise not specified here. This section treats only the three instruments named above; a reader following §9.6.20’s cross-reference to chapter 03 for any of the others will not find them, and §9.6.21’s coverage table records that.