0. Registry Classification
| Field | Entry |
|---|---|
| Restoration Arc ID | RA-043 |
| Name | Legitimacy Re-Anchoring |
| Short Name / Alias | Legitimacy Repair |
| Primary Family | Justice / Governance / Legitimacy |
| Secondary Families | Core; Governance; Auditability; Boundary; Coherence; Institutional Design; AI Governance; Security; Economy; CMS |
| Treatment | Canon Parent Arc |
| Status | Canon-Ready |
| Scope | Institutional / AI / Security / Economic / Governance / Civilizational / Cross-Domain |
| Primary U-Layers | U2 / U3 / U4 → U5 / U6 / U7 validation |
| Primary Operators | Au → Π → Σ → FI → Θ → ℛ → Λ → Τ |
| Primary Diagnostics | Au, O, H, BΣ, R, FI, K, ι, MS_Symmetry, legitimacy_baseline, trust_viability, repair_alignment, Φ/O divergence, recurrence |
1. Purpose
1.1 What This Arc Repairs
Legitimacy Re-Anchoring repairs systems where authority, process, institution, interface, policy, governance structure, public role, AI system, security posture, or economic arrangement has lost legitimate grounding.
It applies when legitimacy has drifted away from truth, repair, consent, accountability, boundary integrity, field proof, affected-node reality, or future-compatible governance.
This arc repairs legitimacy drift by:
- identifying the legitimacy claim;
- auditing the basis of authority, trust, consent, repair, and public confidence;
- distinguishing real legitimacy from reputation, compliance, optics, rank, procedural closure, or symbolic accountability;
- restoring truth, boundary, and responsibility anchors;
- routing hidden debt into repair;
- protecting affected nodes from trust extraction;
- ensuring legitimacy recovery follows repair rather than preceding it;
- validating over time that trust becomes earned, not demanded.
Legitimacy Re-Anchoring is the canonical arc for restoring legitimate standing after authority, process, or trust has become detached from coherence.
1.2 Core Restoration Function
This arc restores legitimacy by re-anchoring authority, trust, process, and public standing to truth, auditability, consent, repair, responsibility, field effects, and affected-node boundary integrity.
Legitimacy Re-Anchoring prevents systems from treating confidence, reputation, legality, compliance, or symbolic repair as proof of restored trustworthiness.
2. Use Conditions
2.1 When to Apply
Use this arc when:
- public trust, process trust, institutional trust, or user trust has collapsed or become unstable;
- an authority still claims legitimacy while affected-node reality contradicts that claim;
- an institution seeks reputation recovery before repair is complete;
- apology, transparency report, compliance score, audit, or public statement is being used as legitimacy proof;
- authority is opaque, unreviewable, or protected by rank;
- legitimacy depends on harmed-node participation, forgiveness, silence, or symbolic endorsement;
- governance process completion is treated as public trust restoration;
- a security, AI, platform, or institutional system claims safety, neutrality, accountability, or care while hidden debt remains;
- a system must transition from legitimacy-by-status to legitimacy-by-field proof;
- future cooperation requires trust viability to be earned through repair.
Examples:
- an AI system seeks user trust after memory, boundary, classifier, or policy failures;
- an institution issues public apology while repair obligations remain unfulfilled;
- a governance process claims legitimacy through participation metrics while affected-node burden remains high;
- a security authority claims protection while exposure and false assurance remain;
- an economic platform claims fairness while exit, consent, and burden conditions remain invalid;
- a symbolic community claims moral legitimacy while taboo, projection, or boundary violations remain unresolved.
2.2 When Not to Apply
Do not apply this arc when:
- active harm is still cascading and emergency stabilization is required first;
- truth and causal clarity have not been established enough to anchor legitimacy;
- affected-node boundaries remain unsafe;
- legitimacy recovery would pressure harmed nodes into participation or forgiveness;
- authority path is too opaque and Authority Registry Clarification must occur first;
- the system seeks legitimacy while refusing material repair;
- the correct immediate move is victim-centered restoration, responsibility mapping, or safe decoupling;
- legitimacy has fully collapsed and successor governance or supersession is required instead.
Legitimacy Re-Anchoring must not become legitimacy theater.
2.3 Required Preconditions
Before this arc begins, the following must be true:
| Precondition | Requirement |
|---|---|
| Minimum Stabilization | Acute harm, trust shock, or legitimacy crisis slowed enough for repair review |
| Legitimacy Claim Identified | Authority, process, institution, role, interface, policy, or trust claim is named |
| Truth / Harm Surface Visible | Relevant facts, harms, burdens, and contradictions can be inspected |
| Authority Path Reviewable | Authority, delegation, decision rights, and accountability path can be traced |
| Boundary Protection | Affected nodes are not used to restore legitimacy without consent and repair |
| Repair Path | Hidden debt, boundary damage, responsibility, and prevention obligations can be routed |
| Field Validation Path | Trust viability and legitimacy baseline can be monitored over time |
If required preconditions fail:
Arc cannot validly begin.The system must return to emergency stabilization, truth clarification, audit surface expansion, victim-centered restoration, responsibility gradient mapping, or authority registry clarification.
3. Failure / Damage Signature
3.1 Pre-State Across S
| Variable | Expected Pre-State |
|---|---|
| O — Coherence | Claimed through authority, process, rank, legality, reputation, or symbolic standing while field coherence is unstable |
| H — Hidden Debt | Rising through unpaid repair, trust extraction, procedural closure, rank immunity, or reputation-first recovery |
| ε — Error / Noise | Appears as distrust, refusal, public backlash, appeal loops, disengagement, legitimacy shock, or repeated contradiction |
| ι — Inversion Index | Rising when legitimacy claim substitutes for repair, accountability, or field proof |
| Au — Auditability | Partial around authority, decisions, harm, responsibility, repair obligations, and legitimacy basis |
| µᵢ — Agent Integrity | Threatened when nodes are asked to trust, comply, participate, or forgive before repair |
| BΣ — Boundary Integrity | Damaged when legitimacy recovery pressures affected-node consent, testimony, participation, or trust |
| K — Compatibility / Slack Context | Low when cooperation is demanded before trust viability is earned |
| R — Restoration Capacity | Misdirected toward public confidence, image repair, or process defense rather than repair |
| Φ — Fitness Proxy | Dominant through reputation, approval, compliance, participation, press response, legal defensibility, or public confidence metrics |
3.2 Primary Failure Links
| Failure Mode | Relationship |
|---|---|
| Legitimacy Failure | Primary repair target |
| Legitimacy Shock | Primary repair target |
| Legitimacy Theater | Primary repair target |
| Authority Opacity | Often co-occurs |
| Rank Immunity | Often co-occurs |
| Symbolic Accountability | Often co-occurs |
| Procedural Closure Without Repair | Often co-occurs |
| Trust Extraction | Primary repair target |
| Public Confidence Theater | Primary repair target |
| Restoration Bypass | False-restoration risk |
| Victim Burden Transfer | Often co-occurs |
| Security Theater | Often co-occurs |
3.3 Origin-Layer Localization
| Layer | Role |
|---|---|
| Failure Origin | Usually U3 authority / governance / process, U4 legitimacy narrative / public identity, or U2 consent / boundary / trust interface |
| Visible Symptom Layer | Often U4 public statement, apology, legitimacy claim, safety claim, reputation story, or Φ trust / participation / compliance metric |
| Required Repair Layer | Same or lower than the layer where legitimacy detached from truth, repair, or field effect |
| Validation Layer | U5 / U6 / U7 through delay, affected-node burden, field trust, recurrence, and legitimacy baseline monitoring |
Canon rule:
Legitimacy is earned by traceable truth, bounded authority, fulfilled repair, and field-validated trust — not by reputation, status, confidence, or closure alone.
4. Restoration Objective
4.1 Canonical Objective
Restore legitimacy by anchoring authority and trust to truth, auditability, boundary integrity, responsibility, repair obligations, and field proof.
Formal objective:
Au_legitimacy ↑
authority trace ↑
repair_alignment ↑
BΣ stable or ↑
H_legitimacy ↓
MS_Symmetry ↑
trust_viability tested
legitimacy_baseline ↑ only after repair
Φ/O divergence ↓
recurrence ↓Expanded objective:
Convert legitimacy from claim-based standing into repair-earned standing that can survive audit, contradiction, affected-node feedback, and future field validation.
4.2 Non-Goals
This arc does not aim to:
- restore reputation before repair;
- produce public confidence without structural change;
- make harmed nodes validate the system;
- use apology as trust proof;
- preserve rank immunity;
- confuse legal defensibility with legitimacy;
- reduce criticism without addressing cause;
- repair optics while hidden debt remains;
- demand trust;
- use participation as proof of restored legitimacy.
5. Operator Sequence
5.1 Minimal Operator Scaffold
Au legitimacy / authority trace → Π affected-boundary and trust protection → Σ repair-earned legitimacy invariant → FI field / affected-node correction → Θ reputation-pressure damping → ℛ truth / responsibility / repair anchoring → Λ trust viability test → Τ legitimacy baseline validationUniversal grammar alignment:
Σ + Θ → Π → Au↑ → FI↑ → ℛ(U3/U4/U2 legitimacy layer) → Λ → Τ → Temporal ProofLegitimacy Re-Anchoring may route into Governance-Level Restoration, Authority Registry Clarification, Equality-Conserving Accountability, Future-Compatible Accountability, Victim-Centered Restoration, or Security Theater Correction.
5.2 Operator Step Table
| Step | Operator | Function | Variable Impact | Failure Prevented |
|---|---|---|---|---|
| 1 | Au | Trace legitimacy claim, authority path, harm, responsibility, and repair basis | Au_legitimacy↑ | Authority opacity |
| 2 | Π | Protect affected-node boundary, consent, participation, and trust from extraction | BΣ↑ / H growth↓ | Trust extraction |
| 3 | Σ | Lock invariant that legitimacy follows truth, repair, and field proof | O protected / Φ constrained | Legitimacy theater |
| 4 | FI | Restore field and affected-node feedback as legitimacy-corrective signal | FI↑ | Public confidence theater |
| 5 | Θ | Reduce reputation pressure, urgency, defensiveness, and public optics gain | K/σ↑ / AP↓ | Image-first repair |
| 6 | ℛ | Repair truth, responsibility, boundary, harm, authority, and prevention anchors | H↓ / R_repair-directed↑ | Symbolic accountability |
| 7 | Λ | Test trust viability, authority fit, and cooperation compatibility | trust_viability clarified | Demanded trust |
| 8 | Τ | Validate legitimacy baseline and recurrence over time | legitimacy_baseline↑ / recurrence↓ | Legitimacy snap-back |
5.3 Sequence Notes
This arc is truth-gated, repair-gated, and field-proof-gated.
Legitimacy Re-Anchoring does not manufacture trust. It creates the conditions under which trust can become rational again.
The sequence must distinguish:
reputation
authority
legality
legitimacy
trust
public confidence
process completion
repair-earned standingThe following steps cannot be skipped:
legitimacy claim identification
authority / harm / repair trace
affected-node boundary protection
field feedback restoration
reputation-pressure damping
repair anchoring
trust viability test
temporal proofIf public confidence rises while repair debt remains, the arc has failed.
If legitimacy recovery depends on harmed-node silence or participation, the arc has inverted.
6. Restoration Phases
Phase 0 — Identify Legitimacy Claim
Purpose: Name the authority, process, institution, policy, interface, role, or trust claim needing repair.
Actions:
- identify who or what claims legitimacy;
- identify what authority is claimed;
- identify what trust or cooperation is requested;
- identify what legitimacy was damaged by;
- identify who is affected by the legitimacy claim.
Validation:
legitimacy claim named
authority and trust request visible
affected field identifiedPhase 1 — Audit Authority, Harm, and Repair Basis
Purpose: Make legitimacy inspectable.
Actions:
- trace authority path;
- trace decision rights;
- trace harm or contradiction;
- trace repair obligations;
- trace who benefited and who carried burden;
- trace whether prior legitimacy depended on rank, reputation, opacity, or symbolic standing.
Validation:
Au_legitimacy ↑
authority path visible
repair basis visiblePhase 2 — Protect Affected-Node Boundaries
Purpose: Prevent legitimacy recovery from extracting trust or participation.
Actions:
- protect refusal;
- protect non-participation;
- protect testimony boundaries;
- protect privacy and safety;
- prevent public use of affected-node participation without consent;
- prevent trust from being demanded as proof of restoration.
Validation:
BΣ stable or ↑
trust extraction ↓
affected-node agency protectedPhase 3 — Reduce Reputation and Optics Pressure
Purpose: Stop legitimacy recovery from becoming image repair.
Actions:
- reduce urgency for public closure;
- reduce defensive messaging;
- reduce reputation-first incentives;
- reduce pressure for apology acceptance;
- reduce PR substitution for repair;
- separate public communication from repair completion.
Validation:
AP(t) ↓
Φ pressure ↓
repair no longer subordinated to reputationPhase 4 — Anchor to Truth, Responsibility, and Repair
Purpose: Rebuild legitimacy from real anchors.
Actions:
- correct record;
- disclose authority and decision path where appropriate;
- assign responsibility;
- repair boundary damage;
- repair material or procedural harm;
- restore appeal or review;
- define prevention commitments.
Validation:
repair_alignment ↑
H_legitimacy ↓
R_repair-directed ↑Phase 5 — Restore Field-Corrective Feedback
Purpose: Make legitimacy correctable by reality.
Actions:
- admit affected-node feedback;
- admit contradiction;
- monitor field effects;
- track recurrence;
- track repair completion;
- preserve appeal and review;
- prevent metrics from self-certifying legitimacy.
Validation:
FI_legitimacy ↑
field signal affects legitimacy claim
Φ/O divergence ↓Phase 6 — Test Trust Viability
Purpose: Determine whether renewed trust, cooperation, or authority acceptance is admissible.
Actions:
- test whether repair is sufficient for trust consideration;
- test whether cooperation remains consent-valid;
- test whether authority can be accepted without coercion;
- test whether affected nodes have safe refusal;
- route to reintegration membrane only if appropriate.
Validation:
trust_viability tested
cooperation not assumed
Λ assessed before renewed reliancePhase 7 — Temporal Proof
Purpose: Confirm legitimacy remains anchored over time.
Actions:
- monitor legitimacy baseline;
- monitor hidden debt;
- monitor recurrence;
- monitor rank immunity;
- monitor trust extraction;
- monitor whether public confidence outruns repair again.
Validation:
legitimacy_baseline(t+n) stable or ↑ after repair
H_legitimacy(t+n) ≤ H_legitimacy(t)
Φ/O divergence ↓
recurrence ↓7. Gates
7.1 Required Gates
| Gate | Requirement | Failure Result |
|---|---|---|
| FI-Gate | Legitimacy must remain correctable by field effects and affected-node signal | Arc resets |
| HR-Gate | No certainty that trust or legitimacy is restored without temporal proof | Legitimacy claim blocked |
| MS-Gate | High-status actors cannot define legitimacy around rank, status, or reputation alone | Claim invalid |
| Au-Actuation | Authority, harm, repair, communication, and legitimacy claims must be traceable | Actuation forbidden or provisional |
| BΣ-Gate | Legitimacy recovery must preserve affected-node boundary, consent, and refusal | Arc aborts or reroutes |
| Λ-Gate | Renewed trust, cooperation, authority, or reintegration requires compatibility and repair proof | Renewal blocked |
| ☷ᵢ Principle Gates | Non-negotiable invariants hold | ∅ outcome |
7.2 Gate Failure Rule
If any required gate fails:
∅ — Legitimacy Re-Anchoring cannot validly proceed in that form.The system must either:
- increase auditability;
- repair authority path;
- protect affected nodes;
- complete responsibility mapping;
- route to victim-centered restoration;
- route to governance-level restoration;
- withdraw or downgrade legitimacy claims until repair is proven.
8. Diagnostics
8.1 Required Diagnostic Trends
| Diagnostic | Expected Trend | Meaning |
|---|---|---|
| Au | ↑ | Authority, harm, repair, and legitimacy basis become traceable |
| O | Stable / ↑ | Coherence improves through legitimate repair |
| H | ↓ | Legitimacy-related hidden debt decreases |
| BΣ | Stable / ↑ | Affected-node and process boundaries are protected |
| R | Repair-directed ↑ | Capacity moves toward actual repair |
| FI | ↑ | Field signal corrects legitimacy claims |
| K / σ | ↑ | Trust and cooperation become less coerced |
| ι | ↓ | Legitimacy claim no longer substitutes for repair |
| MS_Symmetry | ↑ | Authority is reviewable across status levels |
| legitimacy_baseline | Stable / ↑ only after repair | Trustworthiness becomes earned |
| trust_viability | Tested / improves only if earned | Cooperation becomes admissible |
| repair_alignment | ↑ | Repair matches responsibility and harm |
| Φ/O divergence | ↓ | Public confidence aligns better with coherence |
| recurrence | ↓ | Legitimacy drift does not regenerate |
8.2 Arc-Specific Diagnostic Thresholds
Suggested thresholds:
Au_legitimacy ↑
authority trace ↑
repair_alignment ↑
BΣ stable or ↑
H_legitimacy ↓
MS_Symmetry ↑
trust_viability tested
legitimacy_baseline ↑ only after repair
Φ/O divergence ↓
recurrence ↓ across U7Legitimacy Re-Anchoring is not complete if:
public confidence improves before repair
trust is demanded rather than earned
affected nodes validate legitimacy under pressure
authority path remains opaque
rank immunity persists
apology substitutes for material repair
legitimacy claim self-certifies through metrics or status9. Anti-Patterns / False Restorations
9.1 Common False Versions
This arc is being simulated, not executed, if:
- public apology replaces repair;
- transparency report replaces accountability;
- participation metrics are treated as trust;
- legitimacy depends on affected-node silence;
- public confidence rises while hidden debt remains;
- authority remains unreviewable;
- rank immunity survives the repair process;
- process completion is treated as legitimacy restoration;
- branding changes while authority geometry remains unchanged;
- trust is requested before proof.
9.2 Named Anti-Pattern Links
| Anti-Pattern | Why It Fails |
|---|---|
| Legitimacy Theater | Performs trustworthiness without repair anchors |
| Public Confidence Theater | Uses approval or communication as repair proof |
| Apology-as-Legitimacy | Treats admission as restored authority |
| Trust Extraction | Demands cooperation or belief before repair |
| Participation-as-Trust | Mistakes engagement for legitimacy |
| Rank-Protected Legitimacy | Lets status define trustworthiness |
| Transparency Without Consequence | Shows information without changing responsibility or repair |
10. Completion Criteria
10.1 Post-State Signature
| Variable | Required Post-State |
|---|---|
| O | Stable or improved because legitimacy is repair-anchored |
| H | Legitimacy-related hidden debt reduced |
| ε | Distrust and contradiction become admissible signal |
| ι | Reduced where legitimacy claim substituted for repair |
| Au | Authority, harm, responsibility, repair, and trust basis traceable |
| µᵢ | Affected-node agency protected from trust extraction |
| BΣ | Boundary, consent, refusal, and participation integrity preserved |
| K | Cooperation and trust become less coerced |
| R | Repair capacity routed to legitimacy anchors |
| Φ | Subordinate to O; reputation, compliance, public confidence, process closure, or legal defensibility cannot certify legitimacy alone |
10.2 Temporal Proof
Legitimacy Re-Anchoring cannot be declared complete until trustworthiness remains field-valid over time.
Template:
Completion requires Au_legitimacy(t+n) ≥ Au_legitimacy(t),
H_legitimacy(t+n) ≤ H_legitimacy(t),
BΣ(t+n) ≥ BΣ(t),
repair_alignment increasing,
and recurrence decreasing across U7.Minimum temporal proof:
- repair obligations are fulfilled or visibly progressing;
- authority remains reviewable;
- trust is not demanded;
- affected-node boundaries remain protected;
- public confidence does not outrun repair;
- legitimacy does not return to rank, reputation, or closure metrics.
10.3 Completion Statement
Canonical format:
This arc is complete only when legitimacy is re-anchored to traceable authority, truth, boundary protection, responsibility, fulfilled repair, field-corrective feedback, and temporal proof — without trust extraction, rank immunity, symbolic accountability, or reputation-first closure.
11. Cross-Links
11.1 Related Restoration Arcs
| Arc | Relationship |
|---|---|
RA-002 — Truth and Causal Clarification | Precursor when facts or cause remain unclear |
RA-004 — Audit Surface Expansion | Companion when legitimacy surface is opaque |
RA-014 — Hidden Debt Reduction | Companion for unpaid legitimacy debt |
RA-017 — U4-to-U6 Validation | Required companion for validating legitimacy claims against field effects |
RA-024 — Dignity-Preserving Transition | Companion when legitimacy repair requires transition |
RA-028 — Security Theater Correction | Companion when safety posture substitutes for legitimacy |
RA-029 — Emergency Power Restoration | Companion when crisis authority damaged legitimacy |
RA-030 — Interface Re-Legitimation | Companion when interface trust must be restored |
RA-040 — Responsibility Gradient Mapping | Required companion when accountability must be source-aligned |
RA-041 — Victim-Centered Restoration | Required companion when affected-node repair is central |
RA-042 — Repair-First Intake | Precursor when first-contact process must be repaired |
RA-044 — Equality-Conserving Accountability | Companion when equality must be preserved without flattening responsibility |
RA-046 — Future-Compatible Accountability | Companion when accountability must survive future audit |
RA-049 — Governance-Level Restoration | Follow-on when legitimacy failure reveals governance structure damage |
RA-050 — Authority Registry Clarification | Companion when authority path is unclear |
11.2 Related Failure Modes
| Failure Mode | Relationship |
|---|---|
| Legitimacy Failure | Repairs |
| Legitimacy Shock | Repairs |
| Legitimacy Theater | Repairs / prevents |
| Authority Opacity | Repairs / exposes |
| Rank Immunity | Repairs / exposes |
| Symbolic Accountability | Repairs / prevents |
| Procedural Closure Without Repair | Repairs / prevents |
| Trust Extraction | Repairs / prevents |
| Public Confidence Theater | Repairs / prevents |
| Restoration Bypass | False-restoration risk |
| Victim Burden Transfer | Often co-occurs |
| Security Theater | Often co-occurs |
11.3 Related Diagnostics
Au, Au_legitimacy, O, H, H_legitimacy, BΣ, R, FI, K, σ(t), ι, MS_Symmetry, legitimacy_baseline, trust_viability, repair_alignment, Φ/O divergence, recurrence11.4 Related Laws / Invariants
INV — Legitimacy must be anchored to truth, repair, boundary integrity, and field proof.
INV — Trust cannot be demanded as a restoration output.
INV — Reputation is not legitimacy.
INV — Legitimacy without auditability becomes authority capture.
LAW — Legitimacy-first repair accumulates hidden debt.
LAW — Rank immunity destroys legitimacy faster than criticism does.
LAW — Public confidence can rise while coherence falls.
LAW — Φ improvement is not O restoration.12. Domain Notes
12.1 AI / Cognitive Infrastructure
Check:
- model trust;
- platform trust;
- AI safety claims;
- memory and privacy legitimacy;
- classifier appeal legitimacy;
- governance transparency;
- user trust after boundary or consent failure;
- authority claims around alignment, helpfulness, neutrality, or safety.
AI legitimacy re-anchoring requires user-facing trust claims to be tied to traceable behavior, repairable boundaries, appealability, consent, and field validation.
12.2 Justice / Governance / Legitimacy
Check:
- public apology;
- institutional trust;
- process legitimacy;
- authority reviewability;
- affected-node repair;
- legitimacy after emergency power;
- legitimacy after rank immunity or process failure.
JGL legitimacy repair requires truth, responsibility, repair, reviewability, boundary integrity, and recurrence reduction before trust recovery is claimed.
12.3 Biology / Medicine
Conceptual systems mapping only.
Legitimacy Re-Anchoring in biological or medical-adjacent systems means ensuring explanatory, professional, institutional, or intervention legitimacy remains anchored to observed state, consent, boundary, and outcomes rather than authority or confidence alone.
Not diagnosis.
Not treatment.
Not medical advice.
12.4 Economy
Check:
- market legitimacy;
- platform fairness;
- contract legitimacy;
- trust after extraction;
- consumer confidence;
- worker confidence;
- public legitimacy after externalized cost;
- whether fairness claims match burden and repair.
Economic legitimacy repair requires exchange, contract, access, and trust claims to be anchored in real exit, consent, transparency, burden repair, and non-extractive participation.
12.5 CMS / Meaning / Archetypes
Check:
- sacred authority;
- teacher / healer / guardian legitimacy;
- group trust after harm;
- symbolic confession;
- public virtue;
- legitimacy through resonance;
- trust demanded through loyalty or belief.
Meaning systems require legitimacy to be field-grounded, boundary-safe, shadow-aware, and repair-valid rather than charisma- or symbolism-based.
13. Machine-Readable Metadata
id: "RA-043"
title: "Legitimacy Re-Anchoring"
aliases:
- "Legitimacy Repair"
family_primary: "Justice / Governance / Legitimacy"
families_secondary:
- "Core"
- "Governance"
- "Auditability"
- "Boundary"
- "Coherence"
- "Institutional Design"
- "AI Governance"
- "Security"
- "Economy"
- "CMS"
treatment: "Canon Parent Arc"
status: "Canon-Ready"
scope:
- "Institutional"
- "AI"
- "Security"
- "Economic"
- "Governance"
- "Civilizational"
- "Cross-Domain"
u_layers:
failure_origin:
- "usually U3 authority / governance / process"
- "often U4 legitimacy narrative / public identity"
- "often U2 consent / boundary / trust interface"
symptom_visible:
- "U4 public statement / apology / legitimacy claim / safety claim / reputation story"
- "Φ trust / participation / compliance metric"
repair_required:
- "same or lower than layer where legitimacy detached from truth, repair, or field effect"
validation:
- "U5"
- "U6"
- "U7"
operators:
scaffold: "Au legitimacy / authority trace → Π affected-boundary and trust protection → Σ repair-earned legitimacy invariant → FI field / affected-node correction → Θ reputation-pressure damping → ℛ truth / responsibility / repair anchoring → Λ trust viability test → Τ legitimacy baseline validation"
sequence:
- "Au"
- "Π"
- "Σ"
- "FI"
- "Θ"
- "ℛ"
- "Λ"
- "Τ"
state_variables:
primary:
- "Au"
- "O"
- "H"
- "BΣ"
- "R"
secondary:
- "FI"
- "K"
- "ι"
- "Φ"
diagnostics:
- "Au_legitimacy"
- "H_legitimacy"
- "MS_Symmetry"
- "legitimacy_baseline"
- "trust_viability"
- "repair_alignment"
- "Φ/O divergence"
- "recurrence"
gates_required:
- "FI-Gate"
- "HR-Gate"
- "MS-Gate"
- "Au-Actuation"
- "BΣ-Gate"
- "Λ-Gate"
- "☷ᵢ"
linked_failure_modes:
- "Legitimacy Failure"
- "Legitimacy Shock"
- "Legitimacy Theater"
- "Authority Opacity"
- "Rank Immunity"
- "Symbolic Accountability"
- "Procedural Closure Without Repair"
- "Trust Extraction"
- "Public Confidence Theater"
- "Restoration Bypass"
- "Victim Burden Transfer"
- "Security Theater"
linked_restoration_arcs:
- "RA-002"
- "RA-004"
- "RA-014"
- "RA-017"
- "RA-024"
- "RA-028"
- "RA-029"
- "RA-030"
- "RA-040"
- "RA-041"
- "RA-042"
- "RA-044"
- "RA-046"
- "RA-049"
- "RA-050"
anti_patterns:
- "Legitimacy Theater"
- "Public Confidence Theater"
- "Apology-as-Legitimacy"
- "Trust Extraction"
- "Participation-as-Trust"
- "Rank-Protected Legitimacy"
- "Transparency Without Consequence"
completion_tests:
- "Au_legitimacy increases"
- "authority trace increases"
- "repair_alignment increases"
- "BΣ stable or increases"
- "H_legitimacy decreases"
- "MS_Symmetry increases"
- "trust_viability tested"
- "legitimacy_baseline increases only after repair"
- "Φ/O divergence decreases"
- "recurrence decreases across U7"
summary: "Legitimacy Re-Anchoring restores trustworthiness after authority, process, institution, interface, policy, or role legitimacy has drifted from truth, repair, consent, accountability, boundary integrity, field proof, or affected-node reality."Final Calibration Rule
Legitimacy Re-Anchoring answers six questions:
What hidden debt is being generated by legitimacy drift, reputation-first recovery, or trust extraction?
What authority, truth, boundary, responsibility, repair, or field-proof path must be restored?
What auditability proves legitimacy is anchored to repair rather than status, confidence, compliance, or public story?
What apology, trust metric, transparency artifact, public statement, authority claim, or reputation signal must remain provisional until repair is proven?
What trajectory becomes viable once trustworthiness is earned rather than asserted?
How is legitimacy re-anchoring proven over time without legitimacy theater, rank immunity, trust extraction, symbolic accountability, or public-confidence substitution?