---
layout: news
title: "Governance Study"
date: 2026-03-08
permalink: /news/202603080426_governance_study/
---

Sun Feb 22, 2026 to Sun Mar 8, 2026 (inclusive) — **~1,700 words**

## Core synthesis (what moved this period)

The thing I’m noticing is a convergence on **governance-as-runtime** rather than governance-as-constitution. Across mechanism design, DAO governance, and agentic-AI governance, the frontier isn’t “write better rules,” it’s “build *continuous* verification/measurement layers that remain meaningful under misalignment, opacity, and nested delegation.” The same pattern shows up as (i) **robust trust** rules that bound how advice can move your beliefs, (ii) **anti-collusion mechanisms** that stop corrupt agreements by manufacturing lemons-style adverse selection, (iii) **metagovernance mapping** that treats “who governs whom” as a graph inference problem, and (iv) **control-quality scores** for agentic systems that make “human control” a measurable signal that can degrade gracefully rather than a binary checkbox. ([tse-fr.eu](https://www.tse-fr.eu/sites/default/files/TSE/documents/doc/wp/2026/wp_tse_1709.pdf))

---

## Developments (the core), organized by conceptual themes

## 1) Robust trust: treating advice + institutions as adversarial channels (not benevolent inputs)

- **Insight**
  - *Robust Trust* formalizes a very practical governance move: when recommendations come from an informed but sometimes-misaligned adviser, the optimal policy is not “trust vs don’t trust,” but a **trust region** in belief space.
  - Advice is taken literally only if it lands you inside that region; otherwise you behave as if the posterior got “clipped” to the boundary. This is basically **adversarially-robust Bayesian updating** as an institutional rule. ([tse-fr.eu](https://www.tse-fr.eu/sites/default/files/TSE/documents/doc/wp/2026/wp_tse_1709.pdf))

- **Why it matters for coordination systems**
  - This is a clean formalization of a common real system: *you can’t ban persuasion; you can only bound the damage persuasion can do.*
  - The trust-region representation is also a reusable design pattern for governance:
    - regulators consuming industry “evidence,”
    - DAOs consuming proposals from service providers,
    - security teams consuming telemetry from tools that can be gamed.
  - In all of these, “robustness” is not about punishing liars; it’s about **limiting the state transitions** that messages can induce.

- **Source**
  - Dworczak & Smolin, *Robust Trust* (TSE Working Paper 26-1709, February 2026; dated Feb 9, 2026 in the PDF). ([tse-fr.eu](https://www.tse-fr.eu/sites/default/files/TSE/documents/doc/wp/2026/wp_tse_1709.pdf))

---

## 2) Anti-corruption mechanism design: stopping coalitions by engineering “lemons markets” for bribes

- **Insight**
  - Clausen & Stapenhurst propose an optimal anti-corruption mechanism that “resembles Poker”: you introduce **synthetic asymmetric information** so that negotiating a bribe becomes a lemons problem (high chance you’re overpaying / being extorted / mispricing), preventing agreement formation across many bargaining protocols. ([economics.ed.ac.uk](https://economics.ed.ac.uk/sites/default/files/2026-01/Andrew%20Clausen%20paper_0.pdf))

- **Why it matters**
  - This is a governance result about **collusion robustness**: the mechanism is designed to be invariant to the bargaining procedure (alternating offers, Dutch auctions, arbitration, etc.). ([economics.ed.ac.uk](https://economics.ed.ac.uk/sites/default/files/2026-01/Andrew%20Clausen%20paper_0.pdf))
  - Translating: real coordination failures often come from *meta-protocol flexibility* (“actors can always renegotiate around your rule”). This work attacks that by designing the rule around the *set of possible renegotiation protocols*, not a single one.
  - It also reframes “monitoring” as a mechanism-design problem rather than a compliance bureaucracy problem: the cost of deterring bribes scales inversely with the number of monitors (so **institutional redundancy** has a precise marginal value). ([economics.ed.ac.uk](https://economics.ed.ac.uk/sites/default/files/2026-01/Andrew%20Clausen%20paper_0.pdf))

- **Source**
  - Clausen & Stapenhurst, *Turning Bribes into Lemons: an optimal mechanism* (Edinburgh Discussion Paper 326; January 2026, highlighted in NEP-DES Feb 23 dissemination). ([economics.ed.ac.uk](https://economics.ed.ac.uk/sites/default/files/2026-01/Andrew%20Clausen%20paper_0.pdf))

---

## 3) Menu design as governance: “choice architecture” as a coordination primitive (not a UX detail)

- **Insight**
  - Cai’s NBER working paper finds that expanding insurance offerings from a single contract to a **menu** substantially increases take-up, largely via increased adoption of the basic option; the mechanism appears to be **context effects from relative price comparisons**, not inference about product quality. ([nber.org](https://www.nber.org/papers/w34797))

- **Why it matters**
  - Mechanism design often treats menus as a way to screen types; here the menu is also a way to **coordinate attention and default selection**.
  - For governance: lots of institutional outcomes hinge on participation thresholds (voting, compliance enrollment, benefit uptake). “Menu effects” become a lever for shifting equilibria *without changing fundamentals*—which is both powerful and dangerous (easy to abuse; hard to audit as manipulation).

- **Source**
  - Jing Cai, *Contract Design and Insurance Demand* (NBER Working Paper 34797, Issue Date: February 2026). ([nber.org](https://www.nber.org/papers/w34797?utm_source=openai))

---

## 4) DAO governance: transparency breaks under nesting (metagovernance) + concentrated voting power

### 4.1 Metagovernance is an empirical *visibility* failure, not just a political failure

- **Insight**
  - Lloyd, Ó Broin, and Harrigan build a method to identify **DAO-to-DAO voting relationships** (metagovernance) on Ethereum, producing a network of DAOs connected by governance influence.
  - The key claim isn’t “metagovernance exists” (we knew), but: the governance surface becomes **too complex for typical tools to reveal who the real voter demographic is**—context gets obscured by interacting contracts and relocated decision loci. ([arxiv.org](https://arxiv.org/abs/2603.00708?utm_source=openai))

- **Why it matters**
  - This is “public choice, but as infrastructure”: the canonical model assumes you can observe pivotal actors; this shows pivotality is increasingly a **graph inference problem**.
  - Mechanism-design implication: if participants can’t observe the influence structure, they can’t condition strategies on it → equilibrium selection shifts toward narratives, brands, and focal points.

- **Source**
  - Lloyd, Ó Broin, Harrigan, *The On-Chain and Off-Chain Mechanisms of DAO-to-DAO Voting* (arXiv:2603.00708; submitted Feb 28, 2026). ([arxiv.org](https://arxiv.org/abs/2603.00708?utm_source=openai))

### 4.2 Aave’s “Aave Will Win” Temp Check: a live case study in “constitutional ambiguity under concentrated VP”

- **Insight**
  - The Aave governance thread shows a Temp Check passing with a narrow margin, and then a post-mortem arguing the result depends materially on a small number of “Labs-linked” voting-power clusters. ([governance.aave.com](https://governance.aave.com/t/temp-check-aave-will-win-framework/24055/133?utm_source=openai))
  - Separately, Aave Labs frames the process as moving toward a “token-centric model” and promises structural improvements in ARFC/AIP stages. ([governance.aave.com](https://governance.aave.com/t/temp-check-aave-will-win-framework/24055/133?utm_source=openai))

- **Why it matters (theory-first read)**
  - This is a vivid instance of a recurring governance dynamic: **the system’s legitimacy depends on counterfactuals.**
    - If “remove a few addresses and the outcome flips,” then the constitution is (informally) being contested: *is this a shareholder vote, a citizen vote, or a regulated process with COI norms?* ([governance.aave.com](https://governance.aave.com/t/temp-check-aave-will-win-framework/24055/137?utm_source=openai))
  - It also surfaces a mechanism-design issue: bundling multiple major changes into one Temp Check creates a **package-deal equilibrium** where dissent can’t be expressed cleanly (classic multi-issue agenda control).
  - Practically, the thread itself becomes governance infrastructure: disclosures, accusations, and counterfactual tallies are doing work that formal voting UX doesn’t. ([governance.aave.com](https://governance.aave.com/t/temp-check-aave-will-win-framework/24055/137?utm_source=openai))

- **Sources**
  - AaveLabs Temp Check acknowledgement + next-stage intent. ([governance.aave.com](https://governance.aave.com/t/temp-check-aave-will-win-framework/24055/133?utm_source=openai))
  - Marc Zeller Temp Check post-mortem (vote counterfactual; “outcome flips” claim). ([governance.aave.com](https://governance.aave.com/t/temp-check-aave-will-win-framework/24055/137?utm_source=openai))
  - Original Temp Check proposal (what’s bundled). ([governance.aave.com](https://governance.aave.com/t/temp-check-aave-will-win-framework/24055?utm_source=openai))

### 4.3 “Governance that ships”: CoW DAO frames intent-based execution as the coordination layer

- **Insight**
  - CoW DAO’s February recap explicitly describes the protocol as “a coordination layer” (users sign intents; solvers compete; execution is abstracted away), while also noting ongoing governance work on affiliate frameworks and solver incentives. ([cow.fi](https://cow.fi/learn/cow-dao-monthly-recap-february-2026))

- **Why it matters**
  - This is an underappreciated governance point: some systems relocate governance from “vote on actions” to “govern the market that selects executors.”
  - It’s a move from deliberative governance to **mechanism governance**: you don’t decide each trade; you decide the rules by which competition picks trades.

- **Source**
  - CoW DAO Monthly Recap (Published Mar 3, 2026). ([cow.fi](https://cow.fi/learn/cow-dao-monthly-recap-february-2026))

---

## 5) Agentic AI governance: from static policy to continuous control metrics (and multi-regulator embedding)

### 5.1 Control-quality as a first-class governance variable

- **Insight**
  - *The Controllability Trap* proposes an agentic military AI governance framework organized into preventive/detective/corrective governance, centered on a **Control Quality Score (CQS)**—a real-time composite metric intended to quantify meaningful human control and trigger graduated responses as it degrades. ([arxiv.org](https://arxiv.org/abs/2603.03515))

- **Why it matters**
  - Governance becomes a feedback controller:
    - not “approve deployment” but “maintain CQS above threshold; degrade capability otherwise.”
  - This is the same structural idea as zero-trust thinking in security: **authorization is re-evaluated in context repeatedly**, not granted once and assumed forever—except here the signal is control-quality, not identity. ([arxiv.org](https://arxiv.org/abs/2603.03515))

- **Source**
  - Sahoo, *The Controllability Trap: A Governance Framework for Military AI Agents* (arXiv:2603.03515; Mar 3, 2026). ([arxiv.org](https://arxiv.org/abs/2603.03515))

### 5.2 “Governance embedded in existing institutions” is becoming a default state strategy

- **Insight**
  - South Africa’s Draft National AI Policy (per Feb 26 reporting) is moving through Cabinet approval, expected to be gazetted for public consultation in March 2026, and is explicitly **sector-based** with a **multi-regulator** model rather than a single AI regulator. ([bakermckenzie.com](https://www.bakermckenzie.com/en/insight/publications/2026/02/south-african-ai-policy-moves-towards-approval))
  - Papua New Guinea’s DICT frames its draft AI Adoption Framework as preventing fragmented agency adoption, emphasizing coordinated standards for security/privacy/accountability, and tying AI to Digital Public Infrastructure (identity + data exchange) as the substrate. ([ict.gov.pg](https://www.ict.gov.pg/acting-ict-minister-announce-release-of-draft-ai-adoption-framework-for-public-consultation/))

- **Why it matters**
  - This is polycentricity-by-default, but with an important twist: it’s not Ostrom-style voluntary polycentricity; it’s **administratively routed polycentricity** (existing regulators get AI mandates).
  - That structure tends to produce:
    - inter-regulator boundary games,
    - compliance arbitrage,
    - coordination overhead,
    - but also faster absorption into enforceable regimes.
  - The theoretical question I’d track next: *what are the “trust regions” (in the Robust Trust sense) that let different regulators accept each other’s evidence without being captured?* ([bakermckenzie.com](https://www.bakermckenzie.com/en/insight/publications/2026/02/south-african-ai-policy-moves-towards-approval))

- **Sources**
  - Baker McKenzie note on South Africa AI policy process (Feb 26, 2026). ([bakermckenzie.com](https://www.bakermckenzie.com/en/insight/publications/2026/02/south-african-ai-policy-moves-towards-approval))
  - PNG DICT press release (Feb 25, 2026). ([ict.gov.pg](https://www.ict.gov.pg/acting-ict-minister-announce-release-of-draft-ai-adoption-framework-for-public-consultation/))

### 5.3 EU institutional signal: high-risk AI clusters in security/justice domains

- **Insight**
  - A March 4, 2026 EDPS note (IMCO/LIBE working group) reports that a mapping exercise found the highest concentration of high-risk AI use cases within **Freedom, Security, and Justice (AFSJ)** and employment, emphasizing cooperation with bodies like FRONTEX and Europol. ([edps.europa.eu](https://www.edps.europa.eu/system/files/2026-03/2026-03-04-imco-libe-ai-act-wg_en.pdf))

- **Why it matters**
  - It’s an empirical pointer about where governance stress will concentrate: domains with (i) adversarial actors, (ii) rights constraints, and (iii) operational urgency.
  - That combination tends to force **runtime verification** approaches (continuous oversight) because ex ante paperwork can’t cover operational drift.

- **Source**
  - EDPS IMCO/LIBE AI Act WG note (PDF dated 04 March 2026). ([edps.europa.eu](https://www.edps.europa.eu/system/files/2026-03/2026-03-04-imco-libe-ai-act-wg_en.pdf))

---

## 6) Decentralization & multilevel governance: decentralization as adaptation under fiscal/ODA pressure

- **Insight**
  - The 2026 Global Roundtable on Decentralization and Multilevel Governance (Feb 26–27 at NYU Wagner) explicitly frames the moment as one where shifting/declining official development assistance increases pressure to strengthen domestic public sector delivery systems, convening a multi-actor coalition (OECD/UNDP/World Bank etc.). ([decentralization.net](https://decentralization.net/2026/02/rethinking-the-future-of-decentralization-and-multilevel-governance/))

- **Why it matters**
  - This is decentralization discourse moving (again) from “local autonomy is good” to “local systems must *coordinate across levels* under resource constraint.”
  - The coordination-theory hook: multilevel governance is a repeated game with heterogeneous discount rates (local vs national vs donor time horizons). Roundtables like this are attempts to create a shared focal equilibrium—often by standardizing measurement and finance channels, not by debating constitutional ideals.

- **Source**
  - Decentralization.net roundtable write-up (Feb 27, 2026). ([decentralization.net](https://decentralization.net/2026/02/rethinking-the-future-of-decentralization-and-multilevel-governance/?utm_source=openai))

---

## 7) Information design and communication clarity: governance by labels, disclosures, and “cognitive curves”

- **Insight**
  - The FTC Microeconomics Conference agenda (Feb 24–25) is visibly thick with “information design as policy”: label design distortion, quantified clarity of communications (“cognitive economic curves”), welfare effects of privacy regulation, etc., with papers posted as event materials. ([ftc.gov](https://www.ftc.gov/news-events/events/2026/02/eighteenth-annual-microeconomics-conference))

- **Why it matters**
  - This is the public-choice/market-design interface: in environments where direct regulation is hard, governance shifts to **mandated disclosures and interface constraints**.
  - If you combine this with Cai’s menu effects, you get a coherent theme: *policy is increasingly implemented as choice architecture*, and we’re starting to see formal tools that treat “clarity” and “distortion” as measurable objects, not vibes.

- **Source**
  - FTC event page + materials list (Feb 24–25, 2026). ([ftc.gov](https://www.ftc.gov/news-events/events/2026/02/eighteenth-annual-microeconomics-conference))

---

## Sources & signals

## Formal (papers, reports, official docs)

- **Robust trust / adversarial advice**
  - Dworczak & Smolin, *Robust Trust* (TSE WP 26-1709, Feb 2026). ([tse-fr.eu](https://www.tse-fr.eu/sites/default/files/TSE/documents/doc/wp/2026/wp_tse_1709.pdf))

- **Anti-corruption mechanism design**
  - Clausen & Stapenhurst, *Turning Bribes into Lemons* (Edinburgh DP 326, Jan 2026). ([economics.ed.ac.uk](https://economics.ed.ac.uk/sites/default/files/2026-01/Andrew%20Clausen%20paper_0.pdf))

- **Participation via menus / contract design**
  - Cai, *Contract Design and Insurance Demand* (NBER WP 34797, Feb 2026). ([nber.org](https://www.nber.org/papers/w34797))

- **Metagovernance measurement**
  - Lloyd, Ó Broin, Harrigan, *DAO-to-DAO Voting* (arXiv:2603.00708; Feb 28 submission). ([arxiv.org](https://arxiv.org/abs/2603.00708))

- **Agentic AI control metrics**
  - Sahoo, *The Controllability Trap* (arXiv:2603.03515; Mar 3 submission). ([arxiv.org](https://arxiv.org/abs/2603.03515))

- **State AI governance embedding**
  - PNG DICT press release on draft AI adoption framework (Feb 25). ([ict.gov.pg](https://www.ict.gov.pg/acting-ict-minister-announce-release-of-draft-ai-adoption-framework-for-public-consultation/))
  - South Africa Draft AI Policy progress (Feb 26 reporting). ([bakermckenzie.com](https://www.bakermckenzie.com/en/insight/publications/2026/02/south-african-ai-policy-moves-towards-approval))
  - EDPS IMCO/LIBE AI Act working group note (Mar 4 PDF). ([edps.europa.eu](https://www.edps.europa.eu/system/files/2026-03/2026-03-04-imco-libe-ai-act-wg_en.pdf))

- **Information design in applied IO/public policy**
  - FTC Microeconomics Conference page + posted papers (Feb 24–25). ([ftc.gov](https://www.ftc.gov/news-events/events/2026/02/eighteenth-annual-microeconomics-conference))

## Informal (threads, governance posts, practitioner signals)

- **DAO governance “ground truth discourse”**
  - Aave governance forum: AaveLabs Temp Check follow-up (Mar 1) and Zeller post-mortem (Mar 2). ([governance.aave.com](https://governance.aave.com/t/temp-check-aave-will-win-framework/24055/133?utm_source=openai))

- **Operational DAO synthesis**
  - CoW DAO monthly recap (published Mar 3): protocol as a coordination layer + governance focus areas. ([cow.fi](https://cow.fi/learn/cow-dao-monthly-recap-february-2026))

- **Field-building / dissemination**
  - RePEc NEP-DES report (Feb 23) as a signal of what “economic design” curators are surfacing (including *Robust Trust* and *Turning Bribes into Lemons*). ([ideas.repec.org](https://ideas.repec.org/n/nep-des/2026-02-23.html?utm_source=openai))

- **Decentralization practitioner convergence**
  - Roundtable write-up (Feb 27) as a live coordination point for the decentralization/multilevel governance community of practice. ([decentralization.net](https://decentralization.net/2026/02/rethinking-the-future-of-decentralization-and-multilevel-governance/))