Accountability Mechanisms

docs/03-governance/00-overview.md names two of the five properties it states for the Adaptive Governance Framework (AGF) — the network’s layered governance system — as bearing on accountability without specifying a mechanism for either: “Conflict-tolerant” states that conflict is “structured into the system rather than avoided or punished,” and “Transparent” states that “decisions, changes, and governance processes are recorded, published, and made available for network-wide review.” Neither property names a body that holds a decision-maker to account, a metric that is tracked, or a relationship in which one role answers to another. docs/07-human-systems/03-conflict-engagement.md §7.3.3 separately states a five-tier escalation table for conflict between individuals, with a named protocol at each tier, but no trigger condition for moving from one tier to the next, no timeline at any tier, and no mapping of roles to the parties they are accountable to; that gap is not filled here; §7.3.3 remains the corpus’s account of conflict escalation, and this section does not restate it. This section supplies what neither existing passage does: a statement of what is measured, which roles answer to which other roles, and what is stated to follow when a role fails to meet what is expected of it.

Source and provenance. The material below is drawn from a staged extraction of ~/code/mtu-to/, an unreviewed single-pass output describing the Member Trust Union (MTU) — the network’s credit-union-like financial institution. docs/13-member-trust-union/00-overview.md presents the MTU as “a domain-specific implementation of the Humanized Autonomous Organization (HAO) — the network’s coordinating framework” in its opening summary, and states in §13.8 that the MTU is “a HAO instance in its own right” rather than a subordinate layer of one; that framing is this section’s basis for drawing on MTU-specific source material to describe accountability design in the chapter that otherwise treats the network’s governance in general terms. Two source files within the extraction bear on accountability specifically: mtu-8-5-accountability-mechanisms.md, read in full for this section, and mtu-8-6-adaptation-and-evolution-processes.md, checked and excluded (see the note at the end of this section). The staging extraction describes the material as “deliberately thin” and states that stripping bullet lists naming a category with no attached actor, trigger, or consequence “removed… taxonomy padding” rather than substantive content the writer chose to omit. That thinness carries through to what follows: several of the categories below are named with no mechanism stated for how they operate, and the extraction is explicit that none of the three MTU source files it drew on contains a quantified figure, a stated timeline, or a stated consequence for any accountability relationship it names. Where this section states that the source is silent, that silence is the extraction’s own finding, not a gap introduced in restating it.

A. Accountability Relationships

The source names four accountability relationships directly, each under its own heading in a section titled “Specific Accountability Relationships”: governance-to-member, staff-to-governance, MTU-to-community, and cross-level — a local unit’s accountability to the network above it. This is the one place in the source that states a role-to-role accountability pairing rather than a category list, and it is retained here for that reason.

Each pairing in the source carries sub-bullets naming a category with no attached mechanism — for example, “Result Delivery: Achievement of desired outcomes” under one of the four headings — and states no process by which one party in the pair actually holds the other to account: no reporting requirement, no review body, no consequence tied to the relationship. Only the pairing itself is stated here; the category labels beneath each one are not, on the basis that a label naming what accountability is for is not itself a mechanism for how it operates.

B. What Is Measured: Transparency Artifacts

The source’s most concrete content on this topic is a list of named transparency artifacts, under a heading “Transparency Systems”: performance dashboards, decision documentation, financial and resource-use transparency, and impact reporting. The source names each artifact and states no more: no specific indicator or metric populates the “performance dashboards” entry, and no reporting cadence is stated for any of the four.

C. Named Accountability Bodies

Under a heading “Accountability Roles,” the source names five bodies: Ethics Committees, Performance Review Teams, Audit Functions (described as independent), Member Voice Channels, and Supervisory Positions, the last described as staff-facing. The source states no composition for any of the five, no appointment process, and no reporting line — it does not say who sits on an Ethics Committee, who appoints an Audit Function, or to which of the four relationships in §3.3.A any of the five bodies belongs.

D. Peer Accountability

The source names a further channel, described as “team-based” and operating through “structured peer feedback systems,” and distinguishes it explicitly from the hierarchical relationships named in §3.3.A. Beyond the label and the distinction, the source states no mechanics for how peer feedback is structured, how often it occurs, or what is done with it.

E. What Follows

The source states that a “Consequence Framework” exists, and names two components of it: “Progressive Intervention,” described only as “graduated approaches to serious concerns,” and “Pattern Address,” described only as “response to recurring issues.” This is the only place in the source that gestures at a consequence for an accountability failure, and the source is silent beyond the two labels themselves. It does not state what a graduated approach consists of at any step, whether a step carries a defined duration, or what “response” means for a recurring issue — no suspension, removal, restitution, or other named sanction is stated at any tier, and no source states what triggers movement from one component of the framework to the other. This section records that silence rather than supplying a threshold, a deadline, or a penalty the source does not state.

Excluded from this section. mtu-8-6-adaptation-and-evolution-processes.md states a four-stage pipeline for revising governance rules — proposal development, review, approval, implementation planning — but names no actor for any stage: no source states who may initiate a proposal, what body reviews it, or what approval threshold applies. This is a rule-amendment process rather than an accountability relationship, and it falls outside what §3.3.A to §3.3.E state; it is not brought in here. The staging extraction separately notes that the source’s only statement of a varying approval threshold — higher thresholds for a fundamental change, more accessible ones for routine refinement — appears solely inside a fabricated attributed quotation in the underlying source, and the extraction drops it rather than presenting it as fact; this section does not reintroduce it.

Boundary with chapter 09. The accountability relationships, bodies, and consequences named above are governance design: who is answerable to whom, and what the source states or leaves silent about what follows. docs/09-adversarial-analysis/02-governance-capture.md §9.2.9 and docs/09-adversarial-analysis/03-framework-capture.md treat a different question — accountability mechanisms as something a capture pattern can be turned against, stating the case in which “the model’s accountability mechanisms are being asked to act against the people who defined them.” That question, and the detection and resistance mechanisms chapter 09 catalogs against it, are not treated here.