1) Diagnostic Identity

Diagnostic Name: Legitimacy Baseline

Short Name / Symbol: L₀(t)

Diagnostic Class: Legitimacy / Trust Floor / Governance Coherence / Repair Confidence / Systemic Permission

Primary Function: Estimate the baseline level of trust, consent, recognition, and confidence a system has before a specific action, claim, repair, decision, constraint, or authority exercise occurs.

Primary Use: Determine whether a system has enough legitimacy reserve to act, correct, govern, constrain, repair, ask for patience, request cooperation, or survive uncertainty without triggering disproportionate resistance, distrust, exit, or legitimacy shock.

Core Risk if Ignored: The system may act as if it still has trust, authority, or permission when its legitimacy floor has already degraded, causing even correct actions to be rejected, misread, resisted, or experienced as coercive.

Core Risk if Overtrusted: The system may treat existing legitimacy as permanent permission, allowing past trust, status, tradition, success, or authority to substitute for current coherence, repair, evidence, and accountability.

2) Mechanical Definition

L₀(t) measures the pre-action legitimacy floor a system is standing on before it asks others to trust, comply, wait, accept repair, accept classification, accept constraint, or continue coupling.

L₀(t) answers:

How much legitimacy does this system already have before it acts?

Legitimacy Baseline is not the same as popularity, approval, authority, reputation, or legal standing.

It is the starting trust condition from which later actions are interpreted.

A system with high L₀(t) can make mistakes, ask for time, revise, or act under uncertainty without immediate collapse because there is enough stored trust and prior coherence.

A system with low L₀(t) may have even accurate actions interpreted through suspicion because prior debt, asymmetry, false closure, poor repair, or inconsistent standards have lowered the trust floor.

A simple form:

low L₀(t) + high-impact actuation ⇒ legitimacy shock risk ↑

L₀(t) becomes especially important before:

authority claims
classification
constraint
repair-complete claims
public narratives
emergency action
re-coupling
irreversible decisions
high-risk binding
resource requests
trust requests

3) What the Diagnostic Measures

Direct Measurement Target

L₀(t) measures:

• baseline legitimacy
• trust floor
• prior confidence in system correction
• perceived right to act
• perceived fairness of process
• perceived reliability of repair
• perceived integrity of authority
• perceived consistency of standards
• confidence that feedback matters
• confidence that appeal is possible
• confidence that memory is accurate
• confidence that constraints are legitimate
• confidence that affected-node reality will be recognized
• confidence that errors will be corrected
• permission reserve before further action

Indirect / Proxy Signals

L₀(t) can be estimated from:

• trust in prior repairs
• recurrence after repair claims
• appeal trust
• feedback trust
• affected-node willingness to engage
• willingness to wait during uncertainty
• willingness to accept provisional explanation
• prior false closure
• unresolved AckDebt
• narrative_metric_gap
• immunity_index
• MS_symmetry_index
• hidden debt exposure history
• consistency of standards
• public/private narrative divergence
• memory integrity
• truth_tolerance
• exit rates or disengagement
• response to authority requests
• degree of default suspicion

What It Does Not Measure

L₀(t) does not directly measure:

• whether the current action is correct
• whether the system deserves trust forever
• whether authority is valid in all contexts
• whether users or affected nodes are required to trust
• whether distrust is always accurate
• whether popularity equals legitimacy
• whether legal authority equals legitimacy
• whether past success guarantees current legitimacy
• whether a low baseline makes repair impossible
• whether a high baseline makes action safe

High L₀(t) means the system has a stronger starting legitimacy reserve.

It does not mean future actions bypass gate checks.

Low L₀(t) means the system starts from reduced trust.

It does not mean all action is forbidden, but action must become more auditable, reversible, humble, and repair-linked.

4) Canonical State Variables Involved

Canonical state vector:

S = {O, H, ε, ι, Au, µᵢ, BΣ, K, R, Φ}

Primary Variables

• O: legitimacy depends on the system being coherently aligned with reality and effect
• H: hidden debt lowers legitimacy baseline over time
• Au: traceability increases legitimacy by making action inspectable
• µᵢ: integrity between claim, action, consequence, and repair sustains legitimacy
• R: reliable restoration capacity raises legitimacy baseline
• BΣ: boundary respect and permission clarity are central to legitimacy

Secondary Variables

• ε: visible errors can lower L₀(t), especially if repeated or unacknowledged
• ι: pseudo-coherence can preserve surface legitimacy until exposure causes shock
• K: compatibility affects whether authority, repair, or coupling remains trusted
• Φ: strong proxy performance can temporarily support legitimacy but may also hide declining O

Variables Commonly Confused With L₀(t)

5) Localization Signature

Primary Legibility Layers

• U4 — Classification / Metrics / Narratives: where legitimacy is explained, justified, claimed, defended, or lost
• U5 — Coordination / Time: where prior timing, delays, response cadence, and recurrence history affect baseline trust
• U6 — Coherence Field: primary layer where shared trust, permission, and legitimacy are felt system-wide
• U7 — Memory / Recurrence: where prior repairs, betrayals, corrections, and false closures accumulate into baseline
• U2 — Configuration / Boundaries: where rights, appeal, authority, permission, and constraint legitimacy are encoded
• U3 — Execution: where actual behavior either sustains or depletes legitimacy

Primary Leverage Layers

• U2: repair appeal, boundary, permission, and accountability structures
• U3: align behavior with claims
• U4: correct narratives and classification overreach
• U5: repair timing, cadence, and closure sequencing
• U6: restore shared coherence and trust field
• U7: correct memory, recurrence records, and false closure

Verification Layers

• U3: does the system act in ways that match its claims?
• U4: does the narrative match evidence?
• U5: does the system respond within trust-preserving windows?
• U6: does trust recover or decline?
• U7: does memory validate or contradict legitimacy claims?
• U2: do affected nodes have real recourse?

Common Mislocalizations

• Treating formal authority as legitimacy
• Treating popularity as legitimacy
• Treating low resistance as trust
• Treating silence as consent
• Treating compliance as legitimacy
• Treating public narrative as trust
• Treating legal permission as coherence permission
• Treating past legitimacy as current legitimacy
• Treating one successful repair as restored baseline
• Treating affected-node distrust as irrational by default
• Treating reputation as repair capacity
• Treating high Φ as high L₀(t)

6) Input Requirements

Required Inputs

To estimate L₀(t), the system needs:

• system or authority being evaluated
• action or claim being considered
• prior repair history
• recurrence history
• affected-node trust state
• hidden debt indicators
• affected variables in S
• Au_eff
• FI_integrity
• MS_symmetry_index
• AckDebt
• narrative_metric_gap
• immunity_index
• truth_tolerance
• appeal access
• memory integrity
• boundary integrity
• history of closure claims versus outcomes

Optional Inputs

These improve precision:

• trust surveys or qualitative trust records
• appeal records
• complaint recurrence
• public/private narrative comparison
• repair validation records
• affected-node interviews
• exit/disengagement data
• feedback-to-action records
• external audit
• historical legitimacy shocks
• time since last repair failure
• authority-consequence maps
• exception distribution
• resource asymmetry
• legal/procedural context
• prior promise tracking
• acknowledgement history
• crisis response history

Missing Input Behavior

If L₀(t) inputs are missing:

• If repair history is unknown, avoid strong legitimacy claims
• If affected-node trust is unknown, treat baseline as under-sampled
• If AckDebt is unknown, do not assume recognition loops are closed
• If FI_integrity is unknown, do not assume trust can be repaired through feedback
• If MS symmetry is unknown, check for hidden legitimacy debt
• If memory integrity is low, legitimacy narratives may be unreliable
• If narrative_metric_gap is unknown, verify story against outcomes
• If immunity_index is high or unknown, legitimacy may be inflated by protected-origin blindness

Default missing-input posture:

treat legitimacy as provisional → increase Au/FI → include affected-node signal → avoid high-impact closure claims

7) Diagnostic States / Ranges

These ranges are qualitative and should be domain-calibrated.

Healthy / Coherence-Supporting Range

The system has enough baseline legitimacy to act, revise, ask for time, or request cooperation while remaining trusted.

Signals:

• prior repairs generally held
• feedback changes the system
• appeal routes are trusted enough
• standards are applied symmetrically
• hidden debt is low or acknowledged
• affected-node signal is included
• memory is accurate
• truth can be named
• authority is paired with accountability
• constraints are experienced as coherent
• trust survives reasonable uncertainty

Recommended posture:

act with ordinary gates
preserve traceability
continue feedback/review
store legitimacy evidence in U7

Watch Range

Legitimacy exists, but the trust floor is thinning or uneven across nodes.

Signals:

• affected nodes cooperate but with caution
• prior repairs are partly trusted
• appeal access exists but confidence is mixed
• standards appear mostly consistent with some concerns
• narrative requires caveats
• unresolved AckDebt remains in pockets
• feedback works inconsistently
• trust differs by rank, role, or subfield
• public story is slightly stronger than evidence

Recommended posture:

increase Au/FI
avoid overclaiming authority
repair acknowledgment gaps
validate before closure
reduce irreversible action

Degraded Range

The legitimacy baseline is low enough that actions are likely to be distrusted, resisted, or interpreted through prior debt.

Signals:

• affected nodes distrust repair claims
• feedback channels are not trusted
• appeal appears performative
• false closure history exists
• standards appear asymmetric
• hidden debt is high
• official memory is contested
• narrative_metric_gap is high
• authority requests patience but has not repaired prior failures
• compliance persists due to dependency or exit cost, not trust

Recommended posture:

pause legitimacy-dependent claims
repair AckDebt and FI
increase auditability
restore MS symmetry
validate repair through affected nodes

Contraindicated:

public certainty
repair-complete claims
high-impact unilateral action
deep coupling
irreversible binding
demanding trust

Critical / Collapse-Prone Range

Legitimacy baseline is near or below the level required for coherent action.

Signals:

• system claims are presumed suspect
• affected nodes exit, resist, or disengage
• official memory is rejected
• external audit is required for trust
• legitimacy shock has occurred or is likely
• authority can act only through force, dependency, or procedure
• repair language is not believed
• truth exposure destabilizes the system
• hidden debt is high and unacknowledged
• formal authority remains but coherence permission is lost

Recommended posture:

stop legitimacy-dependent expansion
preserve evidence
activate independent Au/FI/MS review
repair hidden debt and acknowledgment loops
correct U7 memory
rebuild legitimacy through verified repair

False Positive Risk

L₀(t) may appear low when:

• affected nodes are cautious during real repair
• old hidden debt is surfacing because FI improved
• legitimate criticism is being newly expressed
• the system is in a temporary trust-rebuilding phase
• transparency makes problems more visible
• skepticism reflects transition rather than collapse
• authority is intentionally lowering certainty
• repair has begun but recurrence window has not passed

False Negative Risk

L₀(t) may appear high when:

• compliance hides distrust
• exit cost suppresses resistance
• public narrative is strong
• affected nodes have stopped reporting
• proxy metrics look good
• hidden debt is unmeasured
• appeal exists but is not trusted
• truth is not being tested
• legitimacy is borrowed from past authority
• silence is mistaken for consent

8) Leading Indicators

L₀(t) degradation appears early as:

• people ask for proof earlier
• patience windows shorten
• repair claims are met with caution
• appeal use declines from distrust
• feedback moves private
• official narratives require more defense
• prior cases are invoked more often
• affected nodes ask “why should we trust this?”
• compliance continues but enthusiasm drops
• truth-tellers become more skeptical
• small errors trigger large legitimacy reactions
• apology or explanation no longer settles anything
• standards are compared more frequently
• public/private trust diverges

9) Lagging Indicators

L₀(t) failure has already accumulated debt when:

• legitimacy shock occurs
• affected nodes disengage or exit
• formal authority remains but trust is gone
• external audit becomes necessary
• repair language is treated as theater
• compliance requires force, dependency, or threat
• official memory is rejected
• public narrative collapses
• appeals are abandoned
• recurrence is interpreted as proof of systemic bad faith
• authority cannot ask for patience
• every action is interpreted through past debt

10) Interpretation Rules

How to Read L₀(t)

L₀(t) should be read as:

baseline trust and legitimacy reserve before action

It is not a measure of whether the current action is correct.

A system may have:

• high L₀(t) and bad action
• low L₀(t) and correct action
• high formal authority and low legitimacy
• low popularity and high legitimacy in a constrained domain
• uneven L₀(t) across subfields
• high L₀(t) among beneficiaries and low L₀(t) among affected nodes
• restored L₀(t) only after recurrence-tested repair

What Changes Its Meaning

L₀(t) changes meaning under:

• high AckDebt
• high narrative_metric_gap
• low FI_integrity
• low Au_eff
• low MS_symmetry_index
• high immunity_index
• low truth_tolerance
• low M_int(t)
• high pseudo_damping_risk
• high recovery_asymmetry
• high exit_cost
• high dependency_load
• low EB
• public legitimacy pressure
• prior legitimacy shock

Context Modifiers

High AckDebt: trust floor is lower because recognition remains open.

High narrative gap: story/evidence mismatch erodes baseline.

Weak FI: feedback cannot repair trust.

Low Au_eff: actions are harder to inspect.

Low MS: perceived asymmetry degrades legitimacy.

High immunity: protected-origin blindness lowers trust.

Low truth tolerance: legitimacy depends on suppressed reality.

High exit_cost: compliance is weak evidence of legitimacy.

Low M_int(t): official memory may be distrusted.

Domain Calibration Notes

L₀(t) should be calibrated by domain:

• in engineering: trust in maintainers, architecture decisions, release gates, incident response, postmortems
• in AI: trust in model answers, safety behavior, memory correction, policy decisions, user feedback handling
• in institutions: trust in procedures, repair systems, complaints, governance, leadership, service delivery
• in governance: public trust in authority, legality, remedies, enforcement, accountability, emergency action
• in relationships: trust floor before repair, boundary requests, re-coupling, explanation, or commitment
• in archives: trust in canon status, glossary, source lineage, versioning, diagnostic consistency, editorial process

11) Operator Sequencing Implications

If L₀(t) Is Healthy

Allowed with ordinary gate checks:

• Γ can select action with normal review
• Π can constrain with ordinary legitimacy support
• ℛ can proceed with trust in repair pathway
• Τ can move forward with monitored authority
• U7 can store legitimacy evidence
• Λ / ⊗ can consider coupling if other diagnostics pass
• public narrative can be issued with evidence

Recommended:

Au/FI check → Γ action → ℛ feedback/repair loop → U7 legitimacy memory

If L₀(t) Is Low

Recommended:

pause authority-heavy action → repair evidence/feedback/acknowledgment → restore MS symmetry → validate through affected-node recovery

Or:

act only with high transparency, reversibility, affected-node access, and repair commitments

Avoid or delay:

• demanding trust
• repair-complete claims
• public certainty
• irreversible Π
• durable high-risk binding
• deep coupling
• legitimacy narratives without evidence
• emergency escalation without audit

Operators Recommended Under Low L₀(t)

• Au: increase traceability
• FI: restore feedback correction
• ℛ: perform verified repair
• Ψ: attend to affected-node reality
• Θ: damp certainty and authority posture
• MS-Gate: repair symmetry failures
• Ξ: detect pseudo-legitimacy
• Π: keep action reversible and bounded

Operators Contraindicated Under Low L₀(t)

• Γ hard closure: will likely be rejected or create debt
• Π irreversible constraint: may be experienced as coercive
• ⊗ deep coupling: increases trust demand
• ⊕ composition: embeds low-legitimacy structure
• Τ acceleration: outruns legitimacy repair
• Σ escalation: sacralizes authority without restoration
• ✕ force: may further lower baseline and increase hidden debt

12) Gate Implications

Gates Strengthened By Reliable L₀(t)

• Au-Actuation: trust can be supported with traceability
• FI-Gate: feedback can repair legitimacy
• High Risk Gate: blocks high-risk binding when baseline legitimacy is too low
• MS-Gate: checks symmetry as core legitimacy condition
• ☷ᵢ: ensures principle claims are legitimacy-supporting rather than rhetorical

Gates Weakened If L₀(t) Is Poorly Known

If legitimacy baseline is unknown:

• Au may overestimate trust from documentation
• FI may not detect feedback distrust
• High Risk Gate may allow binding without permission reserve
• MS may miss legitimacy-degrading asymmetry
• ☷ᵢ may invoke principles that are not trusted
• Π may constrain beyond legitimacy support
• Γ may select action that is correct but unreadable as legitimate
• ℛ may be rejected because prior repair failed

Gate Outcomes Affected

Low L₀(t) should push gates toward:

• Pause authority-heavy action
• Increase auditability
• Require affected-node validation
• Require repair evidence
• Require symmetry review
• Require reversibility
• Deny repair-complete claims
• Deny trust-demanding action
• ∅ for high-impact action where baseline legitimacy is insufficient and unrepaired

13) Scaling Behavior

L₀(t) becomes harder to maintain under scale because memory, repair, feedback, and standards become more distributed.

As systems scale:

• affected-node trust diverges across subfields
• official narratives generalize
• local repair failures become global legitimacy debt
• hidden debt accumulates in low-visibility areas
• standards drift
• feedback becomes summarized
• appeal systems become procedural
• public/private trust diverges
• prior failures become durable memory
• legitimacy can be borrowed from reputation until exposure
• one legitimacy shock can propagate system-wide
• authority actions require stronger evidence and repair capacity

Scaling Risks

• legitimacy shock
• compliance without trust
• public/private trust split
• repair theater
• official-memory rejection
• feedback distrust
• appeal abandonment
• authority overreach
• hidden debt accumulation
• trust floor collapse
• narrative legitimacy replacing repair legitimacy
• coercive reliance on formal authority
• asymmetry becoming structural
• affected-node exit

Scaling Requirements

To scale legitimacy safely, systems need:

• trust-state monitoring
• affected-node validation
• repair evidence
• appeal trust tracking
• feedback-to-action proof
• memory integrity
• narrative/evidence alignment
• MS symmetry review
• immunity checks
• AckDebt tracking
• recurrence validation
• public/private narrative comparison
• external audit triggers
• humility in claims
• reversibility in high-impact action
• legitimacy-repair pathways

Scaling Rule

Legitimacy baseline must scale with authority, consequence severity, dependency depth, and repair reliability.

Sanity constraint:

authority_claim > L₀(t) + Au_eff + R_eff ⇒ legitimacy shock risk ↑

If authority claims exceed baseline trust plus traceability and repair capacity, shock risk rises.

Second constraint:

high AckDebt + low L₀(t) ⇒ trust-demand failure ↑

If recognition debt remains high, requests for trust are likely to fail.

Third constraint:

low L₀(t) + irreversible Π ⇒ coercion perception risk ↑

If legitimacy is low and constraints are irreversible, the action may be experienced as coercive even if formally allowed.

14) Interaction / Coupling Behavior

L₀(t) reveals how much trust a coupling starts with before further action.

What It Reveals About Coupling

• whether the system can ask for patience
• whether repair claims will be believed
• whether continued coupling is trusted
• whether truth can be heard without immediate suspicion
• whether authority can make requests
• whether boundary changes will be interpreted as care or control
• whether re-coupling is premature
• whether old debt still frames current interaction

What It Reveals About Boundary Integrity

Boundary integrity depends on legitimacy.

When L₀(t) is low:

• boundary requests may be distrusted
• access requests may feel coercive
• refusal may be interpreted through old debt
• repair may not land
• consent claims require stronger evidence
• BΣ repair must precede deeper coupling
• official permission may not equal experienced legitimacy

What It Reveals About Compatibility

Compatibility requires enough legitimacy reserve for repair, truth, and difference.

A coupling may be unsafe if:

the system asks for trust after repeatedly failing to repair the trust floor

or:

continued participation is interpreted as legitimacy while exit cost is high

Healthy compatibility includes legitimacy that can survive correction and uncertainty.

Relevant Interface Acts

• ↺ Reflection: review trust baseline before action
• ⇩ Relaxation: lower pressure to trust before repair
• ⊘ Attenuation: reduce coupling where legitimacy is low
• ⊙ Alignment: ensure one’s own action matches trust claims
• →? Invitation: request cooperation without assuming entitlement
• ⚕︎ Restorative Override: requires later legitimacy repair
• ✕ Force: sharply lowers L₀(t) unless narrowly justified and repaired

15) Failure Modes Detected

Primary Failure Modes

L₀(t) detects or predicts:

• legitimacy shock
• trust floor collapse
• compliance without trust
• repair rejection
• appeal distrust
• feedback distrust
• authority overreach
• public/private trust split
• official-memory rejection
• narrative legitimacy failure
• false baseline trust
• trust-demand failure
• re-coupling failure
• coercion perception
• affected-node disengagement
• legitimacy debt accumulation

Composite Regimes Where L₀(t) Matters

• Repair Theater: repair claims fail because baseline trust is too low
• Pseudo-Coherent Basin: apparent compliance hides low legitimacy
• Goodhart Collapse: metrics preserve legitimacy narrative while trust falls
• Crisis Loop: low legitimacy makes each repair less believable
• Coercive Fusion: coupling persists through dependency, not legitimacy
• Extraction Regime: affected nodes lose trust while burden continues
• Mission Lock: legitimacy concerns are subordinated to trajectory
• Taboo Lock: legitimacy depends on avoiding certain truths
• LOS: latent distrust governs beneath formal participation

16) Accountability & Reintegration Implications

If L₀(t) Was Ignored

Likely consequences:

• system demanded trust it had not earned
• repair claims were rejected
• correct actions were misread
• affected nodes disengaged
• authority acted beyond legitimacy reserve
• compliance was mistaken for trust
• hidden debt surfaced as legitimacy shock
• official narrative lost credibility
• re-coupling failed
• future repair became harder

Accountability questions:

• What was the trust baseline before action?
• Was prior repair validated?
• Was AckDebt still open?
• Was feedback trusted?
• Were standards symmetrical?
• Was appeal meaningful?
• Did official memory match affected-node memory?
• Did the system ask for trust without evidence?
• Did exit cost hide low legitimacy?
• Did the action exceed the legitimacy reserve?

If L₀(t) Was Misread

Possible misread forms:

• compliance mistaken for trust
• silence mistaken for legitimacy
• popularity mistaken for legitimacy
• authority mistaken for trust
• skepticism mistaken for bad faith
• transparency-induced discomfort mistaken for legitimacy collapse
• repair-in-progress mistaken for failure
• high reputation mistaken for current legitimacy
• legal permission mistaken for coherence permission
• affected-node caution mistaken for refusal to repair

Required Restoration

When L₀(t) failure is found:

identify trust baseline
→ trace prior repair and recurrence
→ resolve AckDebt
→ restore Au/FI/MS pathways
→ correct memory and narrative gaps
→ validate repair with affected nodes
→ rebuild authority through reversible, evidence-linked action

If legitimacy loss was asymmetric, MS-Gate should review whose trust was depleted, whose trust was assumed, and whose trust was used as legitimacy evidence.

17) Cross-Domain Examples

Technical / Engineering

A team says a system is fixed after repeated failed postmortems. Even if the new fix is correct, other teams do not trust the claim.

Diagnostic implication: low L₀(t) makes repair-complete claims fragile.

Operator sequence: evidence trace → recurrence validation → affected-team feedback → U7 repair memory correction.

Institutional / Governance

An institution announces reform after years of unresolved complaints. Affected nodes reject the announcement because prior repair claims failed.

Diagnostic implication: legitimacy baseline is too low for narrative repair.

Operator sequence: AckDebt review → affected-node validation → transparent repair milestones → recurrence tracking.

AI / Algorithmic

An AI system claims a memory correction is complete, but the user has seen repeated misclassification.

Diagnostic implication: L₀(t) around memory correction is low; claims need proof and reversibility.

Operator sequence: show/change memory scope → correction trace → recurrence test → user validation.

Interaction / Relational

One person asks to “just trust me” after repeated boundary misses. The issue is not the current request alone; the baseline trust floor is low.

Diagnostic implication: trust demand exceeds L₀(t).

Operator sequence: acknowledge prior recurrence → repair boundary memory → reduce request pressure → validate through time.

Archive / Framework Design

A module is labeled canon-ready, but prior canon labels were later revised due to missing links. Readers need stronger traceability before trusting the status.

Diagnostic implication: archive L₀(t) for canon labels requires repair through version evidence.

Operator sequence: status provenance → cross-link audit → version notes → recurrence/reader validation.

18) Test Protocols

1. Trust Baseline Test

What is the trust state before this action?

Failure signal: system assumes trust without checking prior debt.

2. Repair History Test

Have prior repairs held?

Failure signal: repair claims recur without recurrence validation.

3. AckDebt Test

What remains unacknowledged?

Failure signal: trust is requested while recognition loops remain open.

4. Feedback Trust Test

Do affected nodes trust feedback pathways?

Failure signal: feedback exists but is not believed to matter.

5. Appeal Trust Test

Do affected nodes trust recourse pathways?

Failure signal: appeal exists but is viewed as performative.

6. Symmetry Test

Are standards trusted as symmetrical?

Failure signal: asymmetry lowers legitimacy baseline.

7. Narrative/Evidence Test

Does the legitimacy story match evidence?

Failure signal: narrative claims outpace repair evidence.

8. Memory Test

Does U7 support the legitimacy claim?

Failure signal: official memory contradicts lived recurrence.

9. Exit-Cost Test

Is continued participation evidence of trust?

Failure signal: participation persists because exit is costly.

10. Authority-Action Fit Test

Does the action exceed the system’s legitimacy reserve?

Failure signal: high-impact action from low baseline trust.

19) Anti-Patterns

• Authority as legitimacy
• Compliance as trust
• Silence as consent
• Popularity as legitimacy
• Reputation as repair
• Legal permission as coherence permission
• Past trust as current trust
• Repair claim as repair evidence
• Apology as restored baseline
• Appeal pathway as appeal trust
• Feedback channel as feedback trust
• Public narrative as legitimacy
• Metric success as trust floor
• Demanding trust before repair
• Closure before recurrence validation
• Affected-node caution as bad faith
• Exit cost ignored
• Formal symmetry as practical legitimacy
• One success as restored baseline
• Force as legitimacy restoration

20) Spec Validation Check

• Is this truly a diagnostic, not an operator? Yes.
• Does it measure state, capacity, risk, or response rather than act directly? Yes.
• Does it map to S? Yes.
• Are U-layers specified? Yes.
• Are leading and lagging indicators separated? Yes.
• Are interpretation risks defined? Yes.
• Are operator sequencing implications clear? Yes.
• Are gate implications clear? Yes.
• Are scaling risks included? Yes.
• Are interaction implications included? Yes.
• Does it avoid new primitives? Yes.

Condensed Archive Summary

L₀(t) Legitimacy Baseline is the diagnostic estimate of the trust, consent, recognition, and confidence floor a system has before it makes an action, claim, repair, constraint, classification, authority request, or coupling move. It does not measure whether the current action is correct; it measures whether the system has enough legitimacy reserve for the action to be received as coherent. Low L₀(t) indicates risk of repair rejection, trust-demand failure, compliance without trust, authority overreach, appeal distrust, feedback distrust, official-memory rejection, coercion perception, and legitimacy shock. Under low L₀(t), the system should pause authority-heavy action, increase auditability, restore FI/MS pathways, resolve AckDebt, correct memory and narrative gaps, validate repair with affected nodes, and use reversible, evidence-linked action before repair-complete claims, irreversible constraints, deep coupling, public certainty, or trust demands.