RA-043 — Legitimacy Re-Anchoring

Open archive search
Archive registry entry

RA-043 — Legitimacy Re-Anchoring

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.

reviewedid: RA-043version: 1.0updated: 2026-05-20
Archive Progress

This section can be read now; registry depth and cross-references are still being strengthened.

Foundation
Online

The section has a stable overview route and basic reader context.

Technical Layer
Online

A deeper technical overview is available.

Registry
Current

102 registry entries are available.

Cross-links
Curating

Related concepts are being connected conservatively for accuracy.

0. Registry Classification

TableScroll
FieldEntry
Restoration Arc IDRA-043
NameLegitimacy Re-Anchoring
Short Name / AliasLegitimacy Repair
Primary FamilyJustice / Governance / Legitimacy
Secondary FamiliesCore; Governance; Auditability; Boundary; Coherence; Institutional Design; AI Governance; Security; Economy; CMS
TreatmentCanon Parent Arc
StatusCanon-Ready
ScopeInstitutional / AI / Security / Economic / Governance / Civilizational / Cross-Domain
Primary U-LayersU2 / U3 / U4 → U5 / U6 / U7 validation
Primary OperatorsAu → Π → Σ → FI → Θ → ℛ → Λ → Τ
Primary DiagnosticsAu, 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:

TableScroll
PreconditionRequirement
Minimum StabilizationAcute harm, trust shock, or legitimacy crisis slowed enough for repair review
Legitimacy Claim IdentifiedAuthority, process, institution, role, interface, policy, or trust claim is named
Truth / Harm Surface VisibleRelevant facts, harms, burdens, and contradictions can be inspected
Authority Path ReviewableAuthority, delegation, decision rights, and accountability path can be traced
Boundary ProtectionAffected nodes are not used to restore legitimacy without consent and repair
Repair PathHidden debt, boundary damage, responsibility, and prevention obligations can be routed
Field Validation PathTrust viability and legitimacy baseline can be monitored over time

If required preconditions fail:

textScroll
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

TableScroll
VariableExpected Pre-State
O — CoherenceClaimed through authority, process, rank, legality, reputation, or symbolic standing while field coherence is unstable
H — Hidden DebtRising through unpaid repair, trust extraction, procedural closure, rank immunity, or reputation-first recovery
ε — Error / NoiseAppears as distrust, refusal, public backlash, appeal loops, disengagement, legitimacy shock, or repeated contradiction
ι — Inversion IndexRising when legitimacy claim substitutes for repair, accountability, or field proof
Au — AuditabilityPartial around authority, decisions, harm, responsibility, repair obligations, and legitimacy basis
µᵢ — Agent IntegrityThreatened when nodes are asked to trust, comply, participate, or forgive before repair
BΣ — Boundary IntegrityDamaged when legitimacy recovery pressures affected-node consent, testimony, participation, or trust
K — Compatibility / Slack ContextLow when cooperation is demanded before trust viability is earned
R — Restoration CapacityMisdirected toward public confidence, image repair, or process defense rather than repair
Φ — Fitness ProxyDominant through reputation, approval, compliance, participation, press response, legal defensibility, or public confidence metrics

TableScroll
Failure ModeRelationship
Legitimacy FailurePrimary repair target
Legitimacy ShockPrimary repair target
Legitimacy TheaterPrimary repair target
Authority OpacityOften co-occurs
Rank ImmunityOften co-occurs
Symbolic AccountabilityOften co-occurs
Procedural Closure Without RepairOften co-occurs
Trust ExtractionPrimary repair target
Public Confidence TheaterPrimary repair target
Restoration BypassFalse-restoration risk
Victim Burden TransferOften co-occurs
Security TheaterOften co-occurs

3.3 Origin-Layer Localization

TableScroll
LayerRole
Failure OriginUsually U3 authority / governance / process, U4 legitimacy narrative / public identity, or U2 consent / boundary / trust interface
Visible Symptom LayerOften U4 public statement, apology, legitimacy claim, safety claim, reputation story, or Φ trust / participation / compliance metric
Required Repair LayerSame or lower than the layer where legitimacy detached from truth, repair, or field effect
Validation LayerU5 / 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:

textScroll
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

textScroll
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

Universal grammar alignment:

textScroll
Σ + Θ → Π → Au↑ → FI↑ → ℛ(U3/U4/U2 legitimacy layer) → Λ → Τ → Temporal Proof

Legitimacy 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

TableScroll
StepOperatorFunctionVariable ImpactFailure Prevented
1AuTrace legitimacy claim, authority path, harm, responsibility, and repair basisAu_legitimacy↑Authority opacity
2ΠProtect affected-node boundary, consent, participation, and trust from extractionBΣ↑ / H growth↓Trust extraction
3ΣLock invariant that legitimacy follows truth, repair, and field proofO protected / Φ constrainedLegitimacy theater
4FIRestore field and affected-node feedback as legitimacy-corrective signalFI↑Public confidence theater
5ΘReduce reputation pressure, urgency, defensiveness, and public optics gainK/σ↑ / AP↓Image-first repair
6Repair truth, responsibility, boundary, harm, authority, and prevention anchorsH↓ / R_repair-directed↑Symbolic accountability
7ΛTest trust viability, authority fit, and cooperation compatibilitytrust_viability clarifiedDemanded trust
8ΤValidate legitimacy baseline and recurrence over timelegitimacy_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:

textScroll
reputation
authority
legality
legitimacy
trust
public confidence
process completion
repair-earned standing

The following steps cannot be skipped:

textScroll
legitimacy claim identification
authority / harm / repair trace
affected-node boundary protection
field feedback restoration
reputation-pressure damping
repair anchoring
trust viability test
temporal proof

If 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:

textScroll
legitimacy claim named
authority and trust request visible
affected field identified

Phase 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:

textScroll
Au_legitimacy ↑
authority path visible
repair basis visible

Phase 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:

textScroll
BΣ stable or ↑
trust extraction ↓
affected-node agency protected

Phase 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:

textScroll
AP(t) ↓
Φ pressure ↓
repair no longer subordinated to reputation

Phase 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:

textScroll
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:

textScroll
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:

textScroll
trust_viability tested
cooperation not assumed
Λ assessed before renewed reliance

Phase 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:

textScroll
legitimacy_baseline(t+n) stable or ↑ after repair
H_legitimacy(t+n) ≤ H_legitimacy(t)
Φ/O divergence ↓
recurrence ↓

7. Gates

7.1 Required Gates

TableScroll
GateRequirementFailure Result
FI-GateLegitimacy must remain correctable by field effects and affected-node signalArc resets
HR-GateNo certainty that trust or legitimacy is restored without temporal proofLegitimacy claim blocked
MS-GateHigh-status actors cannot define legitimacy around rank, status, or reputation aloneClaim invalid
Au-ActuationAuthority, harm, repair, communication, and legitimacy claims must be traceableActuation forbidden or provisional
BΣ-GateLegitimacy recovery must preserve affected-node boundary, consent, and refusalArc aborts or reroutes
Λ-GateRenewed trust, cooperation, authority, or reintegration requires compatibility and repair proofRenewal blocked
☷ᵢ Principle GatesNon-negotiable invariants hold outcome

7.2 Gate Failure Rule

If any required gate fails:

textScroll
∅ — 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

TableScroll
DiagnosticExpected TrendMeaning
AuAuthority, harm, repair, and legitimacy basis become traceable
OStable / ↑Coherence improves through legitimate repair
HLegitimacy-related hidden debt decreases
Stable / ↑Affected-node and process boundaries are protected
RRepair-directed ↑Capacity moves toward actual repair
FIField signal corrects legitimacy claims
K / σTrust and cooperation become less coerced
ιLegitimacy claim no longer substitutes for repair
MS_SymmetryAuthority is reviewable across status levels
legitimacy_baselineStable / ↑ only after repairTrustworthiness becomes earned
trust_viabilityTested / improves only if earnedCooperation becomes admissible
repair_alignmentRepair matches responsibility and harm
Φ/O divergencePublic confidence aligns better with coherence
recurrenceLegitimacy drift does not regenerate

8.2 Arc-Specific Diagnostic Thresholds

Suggested thresholds:

textScroll
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 U7

Legitimacy Re-Anchoring is not complete if:

textScroll
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 status

9. 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.

TableScroll
Anti-PatternWhy It Fails
Legitimacy TheaterPerforms trustworthiness without repair anchors
Public Confidence TheaterUses approval or communication as repair proof
Apology-as-LegitimacyTreats admission as restored authority
Trust ExtractionDemands cooperation or belief before repair
Participation-as-TrustMistakes engagement for legitimacy
Rank-Protected LegitimacyLets status define trustworthiness
Transparency Without ConsequenceShows information without changing responsibility or repair

10. Completion Criteria

10.1 Post-State Signature

TableScroll
VariableRequired Post-State
OStable or improved because legitimacy is repair-anchored
HLegitimacy-related hidden debt reduced
εDistrust and contradiction become admissible signal
ιReduced where legitimacy claim substituted for repair
AuAuthority, harm, responsibility, repair, and trust basis traceable
µᵢAffected-node agency protected from trust extraction
Boundary, consent, refusal, and participation integrity preserved
KCooperation and trust become less coerced
RRepair 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:

textScroll
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.


TableScroll
ArcRelationship
RA-002 — Truth and Causal ClarificationPrecursor when facts or cause remain unclear
RA-004 — Audit Surface ExpansionCompanion when legitimacy surface is opaque
RA-014 — Hidden Debt ReductionCompanion for unpaid legitimacy debt
RA-017 — U4-to-U6 ValidationRequired companion for validating legitimacy claims against field effects
RA-024 — Dignity-Preserving TransitionCompanion when legitimacy repair requires transition
RA-028 — Security Theater CorrectionCompanion when safety posture substitutes for legitimacy
RA-029 — Emergency Power RestorationCompanion when crisis authority damaged legitimacy
RA-030 — Interface Re-LegitimationCompanion when interface trust must be restored
RA-040 — Responsibility Gradient MappingRequired companion when accountability must be source-aligned
RA-041 — Victim-Centered RestorationRequired companion when affected-node repair is central
RA-042 — Repair-First IntakePrecursor when first-contact process must be repaired
RA-044 — Equality-Conserving AccountabilityCompanion when equality must be preserved without flattening responsibility
RA-046 — Future-Compatible AccountabilityCompanion when accountability must survive future audit
RA-049 — Governance-Level RestorationFollow-on when legitimacy failure reveals governance structure damage
RA-050 — Authority Registry ClarificationCompanion when authority path is unclear

TableScroll
Failure ModeRelationship
Legitimacy FailureRepairs
Legitimacy ShockRepairs
Legitimacy TheaterRepairs / prevents
Authority OpacityRepairs / exposes
Rank ImmunityRepairs / exposes
Symbolic AccountabilityRepairs / prevents
Procedural Closure Without RepairRepairs / prevents
Trust ExtractionRepairs / prevents
Public Confidence TheaterRepairs / prevents
Restoration BypassFalse-restoration risk
Victim Burden TransferOften co-occurs
Security TheaterOften co-occurs

textScroll
Au, Au_legitimacy, O, H, H_legitimacy, BΣ, R, FI, K, σ(t), ι, MS_Symmetry, legitimacy_baseline, trust_viability, repair_alignment, Φ/O divergence, recurrence

textScroll
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

yamlScroll
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:

textScroll
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?