Governance Authority Chain¶

Governance institution — instantiates Regress Termination Rule

Defines who holds legitimate authority to finally close recursive approvals or appeals, within what scope, and what it takes to appeal — so an escalation chain terminates by mandate, not by exhaustion or raw power.

"Who says so?" can regress upward as far as "prove it" regresses downward: every approver can be asked to defer to a higher approver, every appeal can be appealed. A Governance Authority Chain ends that upward regress by naming, in advance, who holds the legitimate authority to finally close a question — bounded to a scope, and reachable through a defined ladder of escalation. What makes it THIS mechanism is that its terminus is authority, not evidence or sufficiency: it settles the "higher authority" regress by mandate. Its whole worth hinges on that mandate being legitimate, scoped, and reviewable — otherwise it is just power asserting itself and calling the argument over.

Example¶

An open-source project keeps stalling on contested changes because any decision can be escalated indefinitely. It charters an authority chain. Routine changes are closed by the module maintainer; unresolved technical disputes escalate to a steering council elected by contributors; conduct matters route to a separate code-of-conduct committee; trademark and legal questions go to the foundation board — each a terminal authority for its own scope, so a technical fight cannot be laundered into a governance override. The chain also fixes the appeal burden: to reopen a maintainer's merge, a challenger must file a documented regression or a charter violation within fourteen days; absent that, the decision stands. Escalation now has a top and a clock. A lone maintainer can no longer rule by fiat, and the project can no longer be held hostage by someone who simply refuses to accept "no."

How it works¶

Lay the escalation ladder. Define the levels a question can rise through and the terminal authority at the top for each kind of question.
Bound each authority. State what each level may and may not decide, so an authority legitimate for one scope cannot annex another.
Legitimate, not merely powerful. Ground the terminal authority in a charter, election, or delegation that those bound by it recognize — the difference between closure and coercion.
Set appeal rights. Fix what a challenger must bring, and by when, to move a decision back up the chain — the reopening burden that keeps closure from being either permanent or perpetually contested.

Tuning parameters¶

Ladder depth — how many escalation levels before a terminal authority. Shallow ladders close fast but concentrate power; deep ones distribute it but slow everything down.
Scope partition — how finely authority is split by domain. Fine partitions prevent overreach but create boundary disputes about which authority owns a question.
Terminal concentration — a single decider versus a council or vote at the top. A single decider is decisive but capturable; a body is robust but can deadlock.
Appeal-burden height — how hard it is to reopen a closed decision. High burdens buy stability and risk entrenchment; low burdens keep authority accountable and invite churn.

When it helps, and when it misleads¶

Its strength is giving approvals and appeals a legitimate stopping point: escalation terminates at a chartered authority rather than at whoever outlasts the others, and bounded scope keeps that authority from metastasizing. It is indispensable wherever recursive approval or appeal would otherwise never close.

Its degenerate form is exactly the risk the archetype warns of — an unbounded or unaccountable chain becomes power assertion, closing questions by mandate that the mandate never actually covered. Over-centralization stalls the organization; a captured terminal authority closes everything in one interest's favor. And the chain is run backwards through forum-shopping: routing a decision to the authority already known to favor your side.^[1] The discipline that keeps it honest is to charter and bound each authority, hold real appeal rights, and keep the chain itself reviewable rather than self-perpetuating.

How it implements the components¶

authority_boundary — it names who may finally close each kind of question and, just as importantly, the limits of that authority.
decision_scope_boundary — different terminal authorities own different scopes, keeping any one closure local to its domain rather than a universal writ.
burden_of_reopening — the appeal rights fix what a challenger must produce, and by when, to move a closed decision back up the chain.

It does not judge whether the supporting evidence is sufficient (stopping_criterion → Decision Closure Criteria), type a demand or assign who must prove a substantive claim (link_type_distinction → Burden-of-Proof Rule), or enumerate the real-world events that reopen a decision (reopening_condition → Review Trigger Register).

Instantiates: Regress Termination Rule — it terminates the authority regress at a legitimate, scoped decider.
Sibling mechanisms: Burden-of-Proof Rule · Decision Closure Criteria · Evidence Sufficiency Rubric · Axiom Set · First-Principles Statement · Five Whys with Stop Rule · Research Stopping Rule · Review Trigger Register · Timeboxed Inquiry Record · Assumption Log

Notes¶

An authority chain answers who may close; a Burden-of-Proof Rule answers who must justify before closing. They are complementary — a healthy governance body decides and discharges a burden — but where the two are fused, an authority can close a question by mandate while appearing to have proven its case, which is how legitimate closure quietly slides into bare power.

References¶

[1] The classic guard against an authority closing questions it has no warrant over is separation of powers — bounding each authority to a domain and providing appeal to another. Forum-shopping, the practice of steering a matter to the most favorable authority, is the standard failure this bounding is meant to prevent. ↩