Universal Theories

1) Diagnostic Identity

Diagnostic Name: Recovery Asymmetry

Short Name / Symbol: recovery_asymmetry

Diagnostic Class: Recovery / Restoration Dynamics / Damage-Repair Ratio / Hidden Debt / Forced-Response

Primary Function: Estimate whether damage, degradation, hidden debt, boundary strain, trust loss, or coherence loss accumulates faster than the system can repair, restore, integrate, or recover.

Primary Use: Determine whether a system is becoming debt-bearing because its degradation pathways are faster, easier, cheaper, or more amplified than its restoration pathways.

Core Risk if Ignored: The system may appear repair-capable in principle while actually losing coherence over time because harm, error, strain, or debt accumulates faster than repair can land.

Core Risk if Overtrusted: Any slow or difficult recovery may be treated as failure, even when repair is genuinely occurring at deeper layers, requires longer recurrence windows, or is intentionally paced to preserve coherence.

2) Mechanical Definition

recovery_asymmetry measures the imbalance between the rate, ease, or magnitude of degradation and the rate, ease, or magnitude of repair.

recovery_asymmetry answers:

Does this system break faster than it heals?

Recovery Asymmetry is not simply “low restoration capacity.”

It compares two directional processes:

damage / degradation / debt accumulation
versus
repair / restoration / debt reduction

A system may have meaningful R_eff, but still high recovery asymmetry if:

damage propagates quickly
repair requires slow coordination
boundary harm lands instantly
trust repair requires time
memory contamination persists
feedback is delayed
repair does not reach the origin layer
hidden debt grows faster than it is surfaced

Recovery Asymmetry becomes critical when systems repeatedly survive stress but do not return to baseline. Each cycle leaves residue.

A simple form:

damage_rate > repair_rate ⇒ H↑ over cycles

3) What the Diagnostic Measures

Direct Measurement Target

recovery_asymmetry measures:

damage accumulation rate
repair completion rate
hidden debt growth versus reduction
degradation speed versus restoration speed
boundary damage versus boundary repair
trust loss versus trust rebuilding
memory contamination versus memory correction
classification error spread versus correction propagation
coupling damage propagation versus repair propagation
feedback delay versus damage speed
recurrence speed versus recurrence repair
repair cost compared to damage cost
whether harm is easier to create than correct
whether error spreads faster than truth
whether constraints can repair what they allow to break

Indirect / Proxy Signals

recovery_asymmetry can be estimated from:

time-to-damage versus time-to-repair
recurrence after repair
repair backlog growth
boundary strain accumulating faster than repair
trust declining faster than restoration
error propagation through dependencies
correction lag across downstream systems
memory update lag
affected-node recovery time
ratio of incident frequency to repair completion
ratio of breach impact to boundary repair capacity
visible ε reduction without H reduction
repeated “fixed” issues returning
repair requiring more effort each cycle
damage spreading automatically while repair requires manual effort
high Gain_stack amplifying degradation faster than R_eff

What It Does Not Measure

recovery_asymmetry does not directly measure:

whether damage was intentional
whether repair is absent
whether recovery is impossible
whether slow recovery means failure
whether all damage should be prevented
whether the system lacks any restoration capacity
whether degradation is morally meaningful by itself
whether visible repair equals hidden debt repair
whether recurrence means no repair occurred
whether repair should be rushed

High recovery_asymmetry means degradation outruns restoration.

It does not mean restoration is absent.

Low recovery_asymmetry means repair keeps pace with or exceeds degradation.

It does not guarantee coherence if both damage and repair are operating around the wrong target.

4) Canonical State Variables Involved

Canonical state vector:

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

Primary Variables

H: hidden debt rises when repair fails to keep pace with degradation
R: restoration capacity is the core counter-force to damage accumulation
O: coherence depends on net recovery across cycles
ε: visible error may show damage but may not capture hidden debt accumulation
BΣ: boundary damage often happens faster than boundary repair
Au: auditability affects whether repair can locate and reduce damage quickly enough

Secondary Variables

ι: pseudo-recovery risk rises when visible repair hides net debt accumulation
µᵢ: integrity degrades when consequences persist longer than correction
K: coupling can amplify damage propagation faster than repair propagation
Φ: proxy recovery may mask real O/H recovery failure

Variables Commonly Confused With recovery_asymmetry

Variable / Diagnostic	Difference from recovery_asymmetry
R_eff	Usable repair capacity; recovery_asymmetry compares repair capacity to actual damage/debt accumulation
𝓓(t) Damping	How disturbance settles after shock; recovery_asymmetry measures damage-vs-repair imbalance across cycles
τ_resp(t)	Delay to response; high latency can create recovery asymmetry
stress_divergence	Difference under stress; recovery_asymmetry measures whether recovery catches up afterward
repair_durability	Whether repair persists; recovery_asymmetry includes whether damage returns faster than repair holds
recurrence_rate	How often failure returns; recurrence may indicate asymmetry but is not identical
AckDebt	Unclosed recognition debt; can contribute to recovery asymmetry
Low ε	Visible error reduction may occur while recovery asymmetry remains high through H accumulation

5) Localization Signature

Primary Legibility Layers

U1 — Power / Budgets: resource imbalance between damage load and repair capacity
U3 — Execution: where damage and repair manifest as action, patching, service, behavior, or process change
U5 — Coordination / Time: where repair sequencing, latency, and backlog determine whether recovery keeps pace
U6 — Coherence Field: where net recovery or net degradation becomes visible across the system
U7 — Memory / Recurrence: where residue, recurrence, repair durability, and debt accumulation persist
U8 — Environment / Forcing: where external stress may accelerate damage faster than repair

Primary Leverage Layers

U1: increase repair resources or reduce damage load
U2: redesign constraints, boundaries, and permissions to reduce damage generation
U3: repair execution pathways
U4: correct classifications and metrics that hide net damage
U5: shorten repair sequencing and reduce latency
U7: repair memory, recurrence, and residue

Verification Layers

U3: did behavior or process recover?
U5: did repair arrive before damage compounded?
U6: did coherence recover, or only visible function?
U7: did recurrence decline and residue clear?
U1: were repair resources proportional to damage load?

Common Mislocalizations

Treating visible repair as net recovery
Treating low ε as low H
Treating repair activity as repair completion
Treating apology or acknowledgment as restoration
Treating performance recovery as trust repair
Treating patching as origin-layer repair
Treating recurrence as a new event
Treating damage speed as unavoidable while repair speed is ignored
Treating slow repair as unwillingness when repair is under-resourced
Treating boundary rupture as sudden when strain accumulated
Treating high R as high R_eff under the relevant damage pathway

6) Input Requirements

Required Inputs

To estimate recovery_asymmetry, the system needs:

damage or degradation pathway
repair pathway
damage rate or recurrence rate
repair rate or recovery time
affected variables in S
hidden debt indicators
visible error indicators
restoration capacity R_eff
reaction latency τ_resp(t)
memory half-life τ_m(t)
recurrence data
boundary strain data
affected-node recovery data
whether repair reaches origin layer
whether repair reduces H or only ε
whether damage propagates through coupling

Optional Inputs

These improve precision:

incident timeline
repair backlog
time-to-damage
time-to-detect
time-to-repair
time-to-restore-trust
post-repair stress test
recurrence interval
damage spread map
repair spread map
coupling map
dependency load
gain stack
affected-node cost
memory correction records
feedback-to-action data
restoration resource map
boundary repair records
long-term coherence indicators

Missing Input Behavior

If recovery_asymmetry inputs are missing:

If hidden debt is unknown, do not infer recovery from visible repair
If repair completion is unknown, treat recovery as provisional
If recurrence data is missing, extend validation window
If damage spread is unknown, repair burden may be underestimated
If affected-node recovery is missing, recovery may be overestimated
If repair layer is unknown, repair may be mislocalized
If coupling is unmapped, damage propagation may be hidden
If Au_eff is low, both damage and repair estimates are provisional
If Φ improves but O is unknown, check proxy recovery

Default missing-input posture:

map damage pathway → map repair pathway → compare rates → verify H reduction → validate recurrence

7) Diagnostic States / Ranges

These ranges are qualitative and should be domain-calibrated.

Healthy / Coherence-Supporting Range

Repair keeps pace with or exceeds degradation, and recovery reaches the relevant layer.

Signals:

damage is localized quickly
repair reaches origin layer
H decreases, not only ε
recurrence declines
boundary strain repairs over time
affected-node recovery occurs
repair backlog remains manageable
memory updates prevent repeat damage
stress retesting shows improved resilience
O recovers or increases across cycles

Recommended posture:

continue ℛ
validate recurrence
store repair learning in U7
allow bounded Δ retesting

Watch Range

Repair is occurring but only barely keeps pace, or some damage pathways recover more slowly.

Signals:

repair backlog grows slowly
recurrence declines but persists
affected-node recovery is delayed
visible error repairs faster than hidden debt
boundary repair lags crossing frequency
repair depends on specific people
damage spreads automatically while repair remains manual
repair costs rise over time
stress reactivates partially repaired patterns

Recommended posture:

increase R_eff
reduce damage load
shorten τ_resp(t)
improve Au_eff
repair origin layer
monitor H and recurrence

Degraded Range

Damage accumulates faster than repair can reduce it.

Signals:

recurring failures outpace repair
repair backlog grows
boundary strain accumulates
affected nodes do not recover between cycles
hidden debt increases despite visible fixes
repair becomes increasingly costly
same pattern returns under stress
coupling spreads damage faster than repair
recovery claims rely on Φ or ε only
R_eff is below damage load

Recommended posture:

pause scaling
attenuate coupling
reduce load
increase R_eff
repair damage generator
validate H reduction before closure

Contraindicated:

declaring repair complete
deep coupling
irreversible composition
high Δ
rapid trajectory acceleration
success claims from visible recovery

Critical / Collapse-Prone Range

Damage, debt, or recurrence compounds faster than the system can recover.

Signals:

repair backlog becomes unbounded
affected nodes exit or collapse
boundary rupture occurs
hidden debt becomes active crisis
repair cannot reach origin layer
recurrence normalizes
emergency response replaces restoration
R_eff is saturated or inaccessible
legitimacy of repair collapses
system cannot return to baseline between stress cycles

Recommended posture:

stop nonessential transitions
triage damage
reduce forcing
restore minimal R_eff
rebuild Au/FI
repair origin layer
decompress recurrence loop
validate across multiple cycles

False Positive Risk

recovery_asymmetry may appear high when:

repair is surfacing old hidden debt
deeper repair has delayed visible payoff
affected-node feedback increases because FI improved
temporary slowdown protects long-term coherence
recurrence is weaker or shorter than before
repair is being staged across layers
visible Φ drops because real O repair is prioritized
honest accounting increases visible backlog temporarily

False Negative Risk

recovery_asymmetry may appear low when:

visible ε is patched quickly
hidden H is not measured
affected-node recovery is excluded
recurrence window is too short
trust or boundary repair is ignored
damage is exported to low-visibility nodes
repair burden is carried invisibly by specific people
metrics show recovery while coherence remains degraded
repair claims are stored before validation

8) Leading Indicators

recovery_asymmetry degradation appears early as:

same repair is repeated
backlog grows
repair takes longer each cycle
affected nodes recover more slowly
boundary strain returns quickly
visible fixes land but trust does not
recurrence interval shortens
repair depends on heroic effort
feedback repeats
repair consumes more slack
damage spreads faster than diagnosis
memory updates lag behind incidents
post-repair stress tests fail
hidden debt indicators rise while Φ recovers
repair costs shift downward or outward

9) Lagging Indicators

recovery_asymmetry failure has already accumulated debt when:

crisis loop activates
repair fatigue appears
affected nodes exit
boundary rupture occurs
legitimacy of repair is lost
external intervention is needed
repair backlog exceeds throughput
old failures become normal
system cannot recover baseline
hidden debt surfaces broadly
emergency constraints become permanent
repair theater replaces restoration
damage cost exceeds restoration capacity
recurrence becomes part of identity memory

10) Interpretation Rules

How to Read recovery_asymmetry

recovery_asymmetry should be read as:

context-specific imbalance between degradation rate and restoration rate

It is not a simple measure of whether repair exists.

A system may have:

high R_eff and high recovery asymmetry if damage propagates faster
low R_eff and low asymmetry if damage load is low
visible recovery and hidden recovery failure
fast technical recovery and slow trust recovery
fast boundary breach and slow boundary restoration
low recurrence but high AckDebt
strong local repair and weak system-wide repair propagation

What Changes Its Meaning

recovery_asymmetry changes meaning under:

low R_eff
high τ_resp(t)
low 𝓓(t)
low σ(t)
low Au_eff
high stress_divergence
high dependency_load
high coupling depth
high boundary_strain
low M_int(t)
short τ_m(t)
high Φ − O
weak FI_integrity
high Gain_stack
high U8 forcing
low affected-node visibility

Context Modifiers

Low R_eff: repair cannot keep pace.

High τ_resp(t): damage compounds before response.

Low 𝓓(t): disturbance continues ringing after intervention.

Low σ(t): no buffer exists for recovery.

Low Au_eff: repair targets may be misidentified.

High stress_divergence: damage appears under pressure faster than expected.

Deep coupling: damage spreads through connected nodes.

Short τ_m(t): repairs decay before recurrence is prevented.

High Φ−O: visible recovery may mask real degradation.

Domain Calibration Notes

recovery_asymmetry should be calibrated by domain:

in engineering: incident frequency versus fix durability, bug recurrence, repair backlog, regression rate
in AI: failure recurrence versus eval/tool/model/memory repair propagation
in institutions: harm recurrence versus reform durability, complaint backlog, restoration trust
in governance: public harm versus remedy throughput, emergency cycles, policy repair
in relationships: rupture speed versus repair speed, boundary repair, trust rebuilding
in archives: drift rate versus correction propagation, glossary repair, version consistency

11) Operator Sequencing Implications

If recovery_asymmetry Is Low / Healthy

Allowed with ordinary gate checks:

ℛ can proceed and be validated
Δ stress testing can continue within bounds
Γ can use repair outcomes for selection
Π can recalibrate constraints after repair
Λ / ⊗ can retest compatibility
U7 memory can store repair durability
Τ can proceed if recurrence remains low

Recommended:

ℛ repair → Δ retest → recurrence validation → U7 update → cautious re-scaling

If recovery_asymmetry Is High

Recommended:

pause load/scaling → reduce damage generation → increase R_eff → repair origin layer → validate H reduction over recurrence

Or:

⊘ attenuate coupling → triage active damage → restore slack → shorten τ_resp(t) → rebuild repair pathway

Avoid or delay:

declaring repair complete
high Δ
deep ⊗
irreversible ⊕
rapid Τ acceleration
scaling based on visible recovery
closure from low ε
durable repair-success memory

Operators Recommended Under High recovery_asymmetry

ℛ: restore at origin layer
Π: reduce damage generation and contain spread
⊘ Attenuation: reduce coupling load
Au: identify damage/repair pathways
Γ: prioritize highest-leverage repair
Θ: damp overcommitment and success claims
Ξ: detect pseudo-recovery
Ψ: attend to hidden affected-node recovery

Operators Contraindicated Under High recovery_asymmetry

Δ high amplitude: creates damage faster than repair
⊗ deep coupling: spreads unrepaired debt
⊕ composition: embeds unresolved asymmetry
Τ acceleration: outruns restoration
Γ closure selection: declares recovery prematurely
Σ escalation: may sacralize unrepaired state
✕ force: creates debt the system cannot recover from

12) Gate Implications

Gates Strengthened By Reliable recovery_asymmetry Reading

Au-Actuation: damage and repair pathways are traceable
FI-Gate: feedback can reveal whether recovery is real
High Risk Gate: blocks high-risk binding when repair has not caught up
MS-Gate: checks whether recovery burden is asymmetrically distributed
☷ᵢ: ensures principle claims do not hide unrepaired debt

Gates Weakened If recovery_asymmetry Is Poorly Known

If recovery asymmetry is unknown:

Au may trace visible repair but miss hidden debt
FI may fail to reveal recurrence
High Risk Gate may allow repair-complete binding too early
MS may miss who carries recovery burden
☷ᵢ may justify closure while restoration is incomplete
Π may remove containment too soon
Γ may select re-scaling prematurely
ℛ may be declared complete without H reduction

Gate Outcomes Affected

High recovery_asymmetry should push gates toward:

Pause scaling
Require recurrence validation
Require H reduction evidence
Require affected-node recovery
Require repair-burden review
Deny repair-complete claims
Deny high-amplitude Δ
Deny irreversible coupling/composition
∅ for high-impact transition when damage outpaces repair

13) Scaling Behavior

recovery_asymmetry becomes more dangerous under scale because damage often scales faster than repair.

As systems scale:

damage propagates through coupling
repair requires coordination
hidden debt becomes distributed
memory correction lags
affected-node recovery becomes harder to see
technical fixes outpace trust repair
exception and backlog growth accelerate
repair burden concentrates in low-visibility nodes
proxy recovery can be reported faster than real recovery
recurrence patterns multiply
repair capacity is fragmented
emergency response normalizes
downstream consequences outlive upstream fixes

Scaling Risks

repair backlog collapse
hidden debt compounding
crisis loop
recovery theater
trust depletion
boundary rupture
recurrence normalization
downstream memory contamination
repair burden export
false resilience
scaling unrepaired debt
coupling cascade
legitimacy shock
emergency normalization
technical recovery / coherence non-recovery split

Scaling Requirements

To scale recovery safely, systems need:

damage-rate tracking
repair-rate tracking
hidden debt indicators
recurrence windows
affected-node recovery measures
repair backlog visibility
origin-layer repair access
repair-burden distribution
coupling damage maps
memory correction propagation
stress retests
damping/ring-down measurement
recovery definitions beyond Φ
repair-complete criteria
post-repair validation
load-reduction triggers

Scaling Rule

Repair capacity must scale faster than damage propagation, hidden debt generation, and recurrence load.

Sanity constraint:

damage_rate > repair_rate ⇒ H↑

If degradation accumulates faster than repair lands, hidden debt rises.

Second constraint:

coupling_depth × damage_rate > R_eff ⇒ propagation risk ↑

If coupling spreads damage faster than repair capacity can reach it, cascade risk rises.

Third constraint:

visible_recovery_rate > H_reduction_rate ⇒ pseudo-recovery risk ↑

If visible performance recovers faster than hidden debt is reduced, recovery may be superficial.

14) Interaction / Coupling Behavior

recovery_asymmetry reveals whether a relation, institution, AI system, archive, or interface can repair damage at least as fast as interaction generates it.

What It Reveals About Coupling

whether coupling creates more damage than repair can resolve
whether one node absorbs unrepaired debt
whether recurrence occurs before repair lands
whether repair burden is symmetrical
whether trust repair lags performance repair
whether deeper coupling is safe
whether exit or attenuation is needed
whether the relation can sustain repeated stress cycles

What It Reveals About Boundary Integrity

Boundary integrity often recovers slower than boundary damage occurs.

When recovery_asymmetry is high:

boundary breaches may land quickly and repair slowly
refusal repair may lag access pressure
old boundary memory may reactivate
BΣ may degrade across cycles
apology or policy may not restore boundary integrity
repeated minor crossings may accumulate as major debt

What It Reveals About Compatibility

Compatibility requires repair symmetry across time.

A coupling may be unsafe if:

each interaction creates more repair demand than the relation can resolve

or:

one node recovers quickly while another carries long-tail debt

Healthy compatibility includes not only good fit, but sustainable recovery dynamics.

Relevant Interface Acts

↺ Reflection: compare damage and repair rates
⊘ Attenuation: reduce interaction load
⇩ Relaxation: reduce pressure to allow recovery
⊙ Alignment: repair one’s own contribution to asymmetry
→? Invitation: re-coupling only after recovery catches up
⚕︎ Restorative Override: only valid if post-action repair capacity exists
✕ Force: high risk when recovery is already slower than damage

15) Failure Modes Detected

Primary Failure Modes

recovery_asymmetry detects or predicts:

hidden debt accumulation
pseudo-recovery
repair backlog growth
crisis loop
boundary repair failure
trust recovery failure
recurrence
repair theater
damage propagation
low R_eff under real load
affected-node depletion
memory correction lag
coupling cascade
technical recovery / coherence non-recovery split
restoration debt
emergency normalization
scaling unrepaired debt

Composite Regimes Where recovery_asymmetry Matters

Crisis Loop: damage recurs faster than learning/repair lands
Repair Theater: visible repair does not reduce hidden debt
Goodhart Collapse: Φ recovers while O/H do not
Extraction Regime: one node carries recovery burden for others
Coercive Fusion: one node must absorb unrepaired harm to preserve coupling
Pseudo-Coherent Basin: system appears stable by exporting recovery burden
Mission Lock: trajectory continues despite net recovery failure
LOS: latent operations generate debt faster than formal repair resolves
Compression Collapse: repair depth compresses while damage compounds

16) Accountability & Reintegration Implications

If recovery_asymmetry Was Ignored

Likely consequences:

damage accumulated despite repeated repair
visible fixes masked hidden debt
affected nodes never fully recovered
repair burden was externalized
recurrence was misread as new failure
trust declined despite performance recovery
boundaries degraded across cycles
repair-complete memory was false
scaling occurred over unresolved debt
crisis loop became normalized

Accountability questions:

How fast did damage land?
How fast did repair land?
Did repair reach the origin layer?
Did H decrease or only ε?
Who carried recovery burden?
Did affected nodes recover?
Did recurrence decline?
Did repair require more effort each cycle?
Was visible recovery mistaken for coherence recovery?
Did coupling spread damage faster than repair?
Was closure declared before recovery completed?

If recovery_asymmetry Was Misread

Possible misread forms:

slow deep repair mistaken for failure
visible repair mistaken for full recovery
old hidden debt surfacing mistaken for new damage
recurrence reduction mistaken for recurrence elimination
affected-node recovery time dismissed as overreaction
repair backlog visibility mistaken for worsening system
temporary Φ drop during real repair mistaken for degradation
repeated feedback mistaken for refusal to move on
emergency stabilization mistaken for restoration

Required Restoration

When recovery_asymmetry failure is found:

map damage and repair rates
→ identify where damage propagates faster than repair
→ reduce damage generation
→ increase R_eff at origin layer
→ repair affected-node recovery pathways
→ correct U7 repair memory
→ validate H reduction and recurrence decline

If recovery burden was asymmetric, MS-Gate should review who was damaged, who recovered, who repaired, and who carried unresolved debt.

17) Cross-Domain Examples

Technical / Engineering

A bug is patched quickly, but every patch creates new edge failures and technical debt accumulates faster than architecture repair.

Diagnostic implication: visible recovery is faster than real structural recovery.

Operator sequence: debt audit → stop patch-only cycle → architecture repair → regression testing → U7 postmortem memory.

Institutional / Governance

A complaint process resolves cases on paper, but affected nodes take far longer to recover and the same issue recurs.

Diagnostic implication: administrative closure outruns restoration.

Operator sequence: affected-node recovery review → repair-burden audit → policy repair → recurrence validation.

AI / Algorithmic

A model issue is fixed in prompt behavior, but memory, tool, evaluation, and downstream classification errors continue.

Diagnostic implication: surface correction is faster than system-wide memory/tool repair.

Operator sequence: trace downstream contamination → repair memory/eval/tool layers → stress retest → U7 correction update.

Interaction / Relational

A boundary breach happens in seconds, but rebuilding trust takes weeks. Repeated small breaches prevent recovery from completing.

Diagnostic implication: boundary damage rate exceeds trust repair rate.

Operator sequence: attenuation → boundary repair → reduce recurrence → validate trust recovery before re-coupling.

Archive / Framework Design

New diagnostics are created faster than glossary, cross-link, status, and dependency updates can repair integration debt.

Diagnostic implication: archive expansion creates drift faster than archive repair can integrate.

Operator sequence: pause expansion → repair glossary/crosswalk → update U7 status → resume with throughput limits.

18) Test Protocols

1. Damage-Rate Test

How quickly does damage, debt, or strain accumulate?

Failure signal: damage lands faster than the system can respond.

2. Repair-Rate Test

How quickly does repair reach the origin layer?

Failure signal: repair is slower than recurrence or propagation.

3. Hidden Debt Test

Does H decrease after visible recovery?

Failure signal: ε drops while H persists or rises.

4. Affected-Node Recovery Test

Do affected nodes recover, or only system metrics?

Failure signal: central recovery claims diverge from affected-node state.

5. Recurrence Test

Does the same failure return before recovery completes?

Failure signal: recurrence interval is shorter than repair interval.

6. Boundary Recovery Test

Does BΣ recover after crossing, breach, or strain?

Failure signal: boundary memory remains damaged after visible repair.

7. Repair Burden Test

Who supplies recovery effort?

Failure signal: harmed or lower-power nodes carry most repair.

8. Coupling Propagation Test

Does damage spread faster than repair across coupling?

Failure signal: connected nodes inherit debt before repair reaches them.

9. Memory Correction Test

Does U7 update after recovery?

Failure signal: old damage or false repair memory persists.

10. Stress Retest

Does the repaired system hold under bounded Δ?

Failure signal: repair collapses under similar stress.

19) Anti-Patterns

Visible fix as recovery
Low ε as low H
Patch as restoration
Apology as trust repair
Case closure as recovery
Performance rebound as coherence
Recurrence as new issue
Repair activity as repair completion
Affected-node recovery ignored
Boundary repair rushed
Technical recovery as full system recovery
Hidden debt unmeasured
Scaling before recovery
Coupling before restoration
Repair burden on harmed node
Emergency stabilization as repair
Trust recovery assumed from behavior change
Memory correction skipped
Recovery declared before recurrence window
Damage speed ignored while repair speed scrutinized

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

recovery_asymmetry is the diagnostic estimate of whether damage, hidden debt, boundary strain, trust loss, memory contamination, or coherence degradation accumulates faster than the system can repair, restore, integrate, or recover. It compares degradation rate against restoration rate, not merely whether repair exists. High recovery_asymmetry indicates risk of hidden debt accumulation, pseudo-recovery, repair backlog growth, recurrence, crisis loops, boundary repair failure, trust depletion, affected-node exhaustion, memory correction lag, coupling cascade, and scaling unrepaired debt. Under high recovery_asymmetry, the system should pause scaling, reduce damage generation, attenuate coupling, increase R_eff at the origin layer, restore slack/Au/FI, verify H reduction, validate affected-node recovery, and retest across recurrence windows before repair-complete claims, deep coupling, irreversible composition, or trajectory acceleration.