LAW-079 — Local Stability Export Law

Open archive search
Archive registry entry

LAW-079 — Local Stability Export Law

If stability depends on externalization, hidden debt is increasing somewhere.

draftid: LAW-079version: 1.0.0updated: 2026-06-16
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

171 registry entries are available.

Cross-links
Curating

Related concepts are being connected conservatively for accuracy.

0. Plain Statement

If stability depends on externalization, hidden debt is increasing somewhere.

Plain-language version:

A system may appear stable because the cost of its stability is paid elsewhere. When local order depends on exporting burden, risk, labor, damage, confusion, instability, or future cost outside the measured basin, the system is not fully coherent. It is stable through externalization.


1. Formal Definition

The Local Stability Export Law states that when a system’s stability depends on externalizing cost, hidden debt is increasing somewhere in the wider field.

This law is the compact discriminator for pseudo-security, extractive economies, institutional order, AI scaling, spiritual authority systems, governance legitimacy, resource allocation basins, biological compensation, and cultural harmony basins.

A system can look stable because:

  • harmed nodes are quiet;
  • downstream teams absorb complexity;
  • future time absorbs maintenance debt;
  • users carry cognitive burden;
  • weaker nodes lose slack;
  • environments absorb substrate damage;
  • public cognition absorbs confusion;
  • invisible labor absorbs execution cost;
  • excluded populations absorb governance burden;
  • biological compensation absorbs overload;
  • contractors, moderators, caregivers, or intermediaries absorb hidden work.

In each case, the question is not only whether the local basin is stable.

The question is whether the stability would remain if the externalized cost were counted, repaired, or internalized.


2. Canonical Form

Core form:

textScroll
stability depends on externalization ⇒ H↑ somewhere

Expanded form:

textScroll
O_local stable ∧ Cost_externalized↑ ⇒ H_field↑ ∧ O_global↓

Diagnostic form:

textScroll
local stability + external burden + low export auditability ⇒ stability-export pattern

Restoration-valid contrast:

textScroll
local stability persists after cost internalization ⇒ stability more likely coherent

Related variables:

textScroll
O, O_local, O_global, H, H_field, H_export, ε, ι, Au, Au_export, R, R_eff, BΣ, K, σ, µᵢ, Φ, Φ_local, Λ, ⊗, Γ, Π, ℛ, Θ, Σ, Ψ, Τ, FI, L

Where:

TableScroll
VariableMeaning in this law
O_localLocal stability or coherence inside the measured basin
O_globalWhole-field coherence after externalized costs are counted
H_fieldHidden debt accumulating somewhere in the larger field
H_exportDebt specifically exported outside the local basin
Cost_externalizedBurden, damage, risk, labor, instability, or future cost moved elsewhere
Au_exportAuditability of the externalized cost
Φ_localLocal success proxy that may improve while costs are exported
ι / ΞInversion when exported-cost stability is called coherence
Basin boundaries that separate counted stability from uncounted burden
K / σSlack / sovereignty often lost by the nodes absorbing externalized cost
R / R_effRestoration capacity required to internalize and repair exported cost
FIFeedback integrity required to hear externalized-burden signals
LLegitimacy; decays when externalized cost becomes visible
ΓClassifies externalized burden as system effect or outside-scope externality
ΠControls, incentives, or procedures that maintain local stability through export
Restoration action that reduces export and repairs burdened fields
ΘHumility prevents local stability from being overclaimed
ΣScope of the basin, measurement field, and externalized cost boundary
ΨField and affected-node feedback reveals hidden cost
ΤTime reveals whether externalized debt returns
ΛCompatibility between the local basin and whole-field coherence
Coupling pathways carrying externalized burden

3. Core Mechanism

The law unfolds when a system’s apparent stability is maintained by moving instability outside the frame of measurement.

Stability export pathway

textScroll
local basin seeks stability
→ destabilizing cost is externalized
→ local order improves or remains stable
→ external field absorbs burden
→ exported cost remains under-audited
→ H_field↑
→ O_global↓
→ rebound / legitimacy shock appears later

Coherent stability pathway

textScroll
local basin seeks stability
→ full cost field is audited
→ externalized burden is counted
→ cost is internalized, repaired, or compensated
→ stability persists without export
→ O_local and O_global align

The core mechanism is:

textScroll
externalization can make local stability appear cheaper than it really is

Detailed mechanism:

  1. A local basin maintains order.

It may be a workplace, platform, model, institution, market, body, culture, security system, governance system, or meaning structure.

  1. A destabilizing cost would threaten that order if counted locally.

The cost may be time, labor, risk, confusion, injury, maintenance, audit, energy, ecological damage, emotional labor, or legitimacy repair.

  1. The cost is externalized.

It is shifted to less visible, less powerful, less measured, less protected, or later fields.

  1. Local stability appears intact.

The basin may claim efficiency, harmony, safety, compliance, growth, maturity, or success.

  1. Hidden debt rises elsewhere.

The burden does not disappear. It accumulates as depleted slack, future repair, ecological damage, user frustration, chronic load, institutional distrust, or security risk.

  1. Whole-system coherence diverges from local stability.

The system looks coherent from one position and incoherent from another.

  1. Time reveals the export.

Debt returns through recurrence, collapse, protest, chronicity, breach, legitimacy shock, or forced redesign.


4. When This Law Applies

This law applies whenever a system appears stable because cost has been moved outside the measured frame.

It is especially important when:

  • local metrics improve while downstream burden rises;
  • stability depends on low-status or invisible labor;
  • users must compensate for system complexity;
  • workers absorb volatility to preserve customer-facing calm;
  • future maintenance absorbs present speed;
  • ecosystems absorb economic cost;
  • harmed nodes remain silent due to exit cost;
  • security systems shift risk to end users;
  • AI systems shift uncertainty to moderators, appealers, or public cognition;
  • governance systems defer cost to future administrations or excluded groups;
  • cultural harmony depends on suppressed feedback;
  • biological function depends on hidden compensation;
  • institutional order depends on procedural exhaustion.

The law applies strongly when:

textScroll
local stability would fail if externalized cost were internalized

or when:

textScroll
stability is measured only where the burden is not carried

Typical domains:

TableScroll
DomainLocal Stability Export Expression
AI systemsPlatform stability depends on users, moderators, annotators, or public cognition absorbing ambiguity and repair burden.
SecurityInternal security posture depends on users or downstream teams carrying complexity and risk.
InstitutionsAdministrative order depends on harmed participants, staff, committees, or future processes absorbing repair burden.
Medicine / biologyVisible function depends on hidden compensation from energy, posture, immune, circulation, or stress pathways.
EconomyProfit or growth depends on labor, ecological, debt, time, or maintenance cost externalization.
GovernancePresent legitimacy depends on future debt, excluded voices, procedural delay, or hidden enforcement burden.
CultureHarmony depends on suppressed feedback, marginalized silence, or emotional labor.
RestorationStability must be tested by asking whether hidden cost has merely moved elsewhere.

5. When This Law Does Not Apply

This law should not be used to reject all distributed work, specialization, delegation, outsourcing, or burden-sharing.

A system can coherently distribute cost when the distribution is visible, consent-valid, resourced, reversible, capacity-matched, and included in the coherence accounting.

False-positive cases:

TableScroll
CaseWhy it is not local stability export
A support team absorbs work with adequate resources, authority, and repair capacityBurden is assigned coherently
Environmental cost is measured, reduced, repaired, and priced into decisionsCost is not hidden
Users receive tools that reduce burden rather than shifting it invisiblyStability does not depend on hidden extraction
Future maintenance is funded and scheduled transparentlyTime cost is accounted for
Care labor is recognized, resourced, and protectedThe burden is not externalized as hidden debt

Important distinction:

Distributed responsibility can be coherent. Externalized cost becomes debt when it is hidden, under-resourced, coerced, or excluded from the system’s stability claim.


6. Diagnostic Signature

Canonical diagnostic:

textScroll
stability depends on externalization ⇒ H↑ somewhere

Warning signature:

textScroll
O_local stable
Φ_local↑
external burden↑
Au_export↓
exit cost↑
O_global↓
⇒ local stability export

Common indicators:

TableScroll
DiagnosticExpected movementInterpretation
O_localstable / ↑Local basin appears stable
Φ_localLocal success proxy improves
Cost_externalizedCost is moved outside measurement
H_fieldHidden debt accumulates somewhere
H_exportExported debt rises outside basin
Au_export↓ / lowExternalized burden is difficult to see
O_globalWhole-field coherence declines
K / σ↓ in burdened fieldSlack and sovereignty drain where cost lands
asymmetricBoundaries separate benefit from burden
FIdegradedExternal feedback is filtered or dismissed
LdivergingLegitimacy differs by observer position
recurrence↑ externallyExternalized cost returns as repeated failure
ι / ΞStability claim becomes inversion
R_effinsufficient externallyRepair capacity does not follow the burden

Additional diagnostics:

TableScroll
DiagnosticUse
Local Stability ExportDetects whether stability depends on externalized burden
Externalized CostIdentifies the cost moved outside the measured basin
Hidden Debt ExportTracks exported debt accumulation
Local-Global Coherence GapCompares local stability to whole-field effects
Debt MigrationShows where burden moves over time
Exported BurdenMeasures who or what pays for local stability
Effective AuditabilityTests whether external cost is visible
Observability DistributionShows whose burden counts
Exit CostMeasures lock-in for burdened nodes
Resource GatekeepingDetects whether resources avoid the burdened field
Legitimacy BaselineDetects observer-dependent legitimacy

7. Failure Pattern

If ignored, this law lets local stability hide field-level debt.

General failure pathway:

textScroll
local stability achieved
→ externalized cost excluded from measurement
→ local success proxy rises
→ external field absorbs burden
→ H_field↑
→ recurrence / legitimacy shock / collapse later

Common failure modes:

  • Local Stability Export — stability is preserved by moving cost elsewhere.
  • Externalized Cost Stability — local order is bought through external burden.
  • Hidden Debt Export — burden becomes invisible system debt.
  • Pseudo-Coherent Basin — basin looks coherent locally while global coherence declines.
  • Incoherence Displacement — instability is moved, not resolved.
  • Debt Migration — hidden cost travels across fields or time.
  • Silent Extraction — unseen work or capacity absorbs the cost.
  • Exit Cost Lock — burdened nodes cannot leave or renegotiate.
  • Normalization Shield — externalized cost becomes normal and escapes audit.
  • Legitimacy Debt — stability loses legitimacy when cost is revealed.
  • Suppressed Potential — the burdened field cannot express its actual capacity.
  • Pseudo-Restoration — local repair optics improve by exporting repair cost.
  • Delayed Collapse — exported burden returns after local stability persists for a time.

Compact failure signature:

textScroll
O_local stable + Cost_externalized↑ ⇒ H_field↑

8. Restoration Implications

Restoration requires testing whether stability survives cost internalization.

The first restoration question is not:

textScroll
Is the local system stable?

The first restoration question is:

textScroll
Would the local system remain stable if the exported cost were counted and repaired?

Restoration priorities:

  1. Identify the local stability claim.
  2. Map the measured basin boundary.
  3. Identify costs excluded from the stability claim.
  4. Trace where those costs land.
  5. Restore observability in burdened fields.
  6. Measure exit costs and power asymmetries.
  7. Internalize, compensate, repair, or redesign externalized burden.
  8. Move resources and restoration capacity toward burdened fields.
  9. Re-evaluate stability after externalized cost is counted.
  10. Time-validate that local stability no longer depends on hidden export.

Relevant restoration arcs:

TableScroll
Restoration ArcWhy it applies
Local Stability AuditTests whether stability depends on externalized burden
Export Channel MappingFinds where cost is routed
Debt Export ReversalStops stability from depending on cost displacement
Hidden Debt ReductionReduces field-level hidden debt
Auditability RestorationMakes externalized cost visible
Observability RedistributionExpands the truth field to include burdened nodes
Boundary ReconstitutionRepairs asymmetric boundaries that export cost
Slack RegenerationRestores capacity to burdened nodes
Exit Cost ReductionAllows burdened nodes to leave or renegotiate
Resource Flow RedesignAligns support with actual burden
Higher-Order Attractor FormationProvides stability not dependent on export
Basin SupersessionReplaces export-dependent stability geometry
Temporal ValidationConfirms repaired stability holds over time

Minimal restoration sequence:

textScroll
identify local stability claim
→ map excluded costs
→ trace burden destination
→ restore Au_export
→ internalize / repair / compensate cost
→ redistribute R_eff
→ test whether O_local and O_global both hold over Τ

Temporal validation requirement:

textScroll
O_local stable
O_global stable or rising
Cost_externalized↓
H_field↓
Au_export↑
burdened-node slack↑
exit cost↓
recurrence↓
legitimacy gap narrows

9. Design Rule

Do not call a system stable until the cost of its stability has been traced.

Operational design requirements:

  • Define the measured basin.
  • Identify local success and stability metrics.
  • Identify excluded costs.
  • Audit downstream, future, environmental, cognitive, labor, and marginalized-field burden.
  • Track slack loss in burdened nodes.
  • Track exit cost.
  • Track resource flow.
  • Treat externalized cost as part of system state.
  • Test whether stability survives cost internalization.
  • Redesign boundaries that export burden.
  • Prevent scale until export debt decreases.
  • Validate over time.

Avoid:

  • calling cost-shifting efficiency;
  • calling silence stability;
  • calling procedural exhaustion resolution;
  • calling downstream burden outside-scope by default;
  • treating unpaid labor as free capacity;
  • treating future maintenance as current success;
  • treating user burden as product simplicity;
  • treating ecological burden as externality;
  • treating excluded populations as outside the legitimacy field;
  • treating biological compensation as recovery;
  • treating local calm as global coherence.

10. Cross-Scale Expressions

TableScroll
Scale / LayerExpression of the Law
U0 — SubstrateStability is achieved by pushing cost into physical, biological, ecological, or infrastructural substrate.
U1 — Energy / capacityLocal capacity is preserved by draining slack elsewhere.
U2 — Boundary / interfaceBoundaries separate counted stability from uncounted burden.
U3 — Process / executionProcesses appear stable by pushing complexity to downstream execution layers.
U4 — Classification / claimExternalized burden is classified as outside-scope, user error, externality, or edge case.
U5 — Time / delayStability is purchased by shifting cost into future maintenance or delayed collapse.
U6 — Field effectAffected-node outcomes reveal the true cost of local stability.
U7 — Recurrence / memoryExternalized cost returns as recurring instability.
U8 — Environment / forcingEnvironmental and field conditions absorb burden until rebound occurs.

11. Examples

Example A — Pseudo-Security Through User Burden

Scenario:

A security system appears stable because users are required to manage complex credentials, alerts, confirmations, and recovery flows. Internal breach metrics improve, but user error, lockouts, support burden, and distrust increase.

Law expression:

textScroll
O_security local stable + user burden↑ ⇒ H_field↑

Interpretation:

Security stability is being purchased by exporting cognitive and operational burden to users.


Example B — Extractive Economic Stability

Scenario:

An economy appears stable because prices, profit, or growth remain strong, but workers, ecosystems, households, suppliers, or future maintenance systems absorb the cost.

Law expression:

textScroll
Φ_economy↑ + Cost_externalized↑ ⇒ pseudo-stability

Interpretation:

The system is not coherent if its apparent stability depends on externalized labor, ecological, or debt burden.


Example C — Institutional Order Through Procedural Exhaustion

Scenario:

An institution reports low complaint volume because reporting pathways are exhausting, opaque, slow, and costly.

Law expression:

textScroll
complaints↓ + pathway burden↑ ⇒ hidden debt↑

Interpretation:

Low complaints do not prove order. The cost of speaking has been externalized to harmed participants.


Example D — AI Product Simplicity

Scenario:

An AI product looks simple and polished because complexity is pushed to moderators, prompt workarounds, user trial-and-error, or unclear appeal systems.

Law expression:

textScroll
Φ_product simplicity↑ + hidden user/moderator labor↑ ⇒ H_export↑

Interpretation:

The interface is locally stable because complexity is absorbed elsewhere.


Example E — Biological Compensation

Scenario:

A body maintains daily function by shifting load to posture, stress pathways, immune activation, digestion, sleep debt, or pain tolerance.

Law expression:

textScroll
visible function stable + compensatory burden↑ ⇒ biological H_field↑

Interpretation:

The system appears stable because another layer pays the cost.


Example F — Governance Stability Through Future Debt

Scenario:

A government maintains present order by delaying infrastructure repair, ecological response, institutional accountability, or fiscal correction.

Law expression:

textScroll
present stability + future cost↑ ⇒ governance H_future↑

Interpretation:

Present stability is debt issuance into time.


12. Relationship to Nearby Laws

TableScroll
Related LawRelationship
LAW-003 — Success Proxy Divergence LawLocal stability metrics can diverge from coherence
LAW-004 — Stability-Coherence Separation LawStability is not coherence when cost is externalized
LAW-005 — Local–Global Divergence LawLAW-079 is the stability-export form of local/global divergence
LAW-006 — Time Validation LawExported stability debt returns over time
LAW-008 — Recurrence Validation LawRecurrence reveals externalized cost
LAW-010 — Hidden Debt Accumulation LawExternalized cost becomes hidden debt
LAW-011 — Hidden Debt Return LawExported cost returns later
LAW-013 — Auditability-Debt LawExternalized cost persists when auditability is low
LAW-015 — Suppressed Auditability Debt LawSuppressing externalized cost creates debt
LAW-017 — Silent Extraction LawStability export often depends on silent extraction
LAW-030 — Slack Sovereignty LawBurdened nodes lose slack and sovereignty
LAW-031 — Observability Collapse LawStability appears coherent when burden is outside view
LAW-032 — Hidden Debt Migration LawExternalized stability is a debt migration pattern
LAW-053 — Wrong-Solution Basin LawStability export may stabilize the wrong basin
LAW-058 — Resource Gatekeeping LawResources may protect the stable local basin rather than burdened fields
LAW-064 — Restoration Debt Reduction LawRestoration must reduce the exported cost
LAW-065 — Pseudo-Restoration LawPseudo-restoration can stabilize locally by exporting debt
LAW-072 — Quiet Minimization Debt LawQuiet minimization hides local stability export
LAW-073 — Restoration Before Scaling LawScaling externalized stability amplifies field debt
LAW-077 — Pseudo-Coherent Basin LawLAW-079 is the compact stability-export discriminator of LAW-077
LAW-078 — Pseudo-Coherent Basin Export LawLAW-078 details channels; LAW-079 gives the diagnostic principle
LAW-080 — Basin Escape Energy LawExternalized stability can raise exit costs
LAW-081 — Higher-Order Attractor LawExport-dependent systems require visible alternatives
LAW-082 — Basin Supersession LawPersistent externalization may require basin redesign
LAW-083 — Normalization Shield LawNormalized externalized cost escapes scrutiny
LAW-084 — Resistance Positionality LawResistance may come from nodes asked to keep absorbing exported cost
LAW-102 — Legitimacy Audit LawLegitimacy must include observers paying the cost
LAW-119 — Basin Self-Defense LawBasins defend the export pattern that preserves stability
LAW-148 — Capital Basin Allocation LawCapital often protects stability-export basins
LAW-149 — Suppressed Potential Measurement LawBurdened fields cannot express potential under externalized cost
LAW-150 — Economic Restoration Geometry LawEconomic restoration requires redesigning externalized stability
LAW-171 — Cancer Local Fitness Basin LawBiological local fitness can export cost to organism-level coherence

Aliases folded into this law:

  • Local Stability Export Law
  • Externalized Stability Law
  • Stability Through Externalization Law
  • Externalized Cost Stability Law
  • Local Stability Debt Law
  • Exported Stability Debt Law
  • Stability Paid Elsewhere Law

Deduplication note:

This law should remain the compact local-stability export discriminator. LAW-077 defines pseudo-coherent basins broadly, LAW-078 specifies export channels and signatures, LAW-080 explains why basin escape becomes costly, LAW-081 defines the need for a higher-order attractor, and LAW-082 defines the restoration method for pseudo-coherent basins.


13. Operator Mapping

TableScroll
OperatorRole in this law
ΓClassifies local stability as coherent, externalized, or pseudo-coherent
ΠMaintains stability through controls, incentives, procedures, or burden routing
ΞCaptures inversion when externally paid stability is named coherence
Coupling pathways carry the burden to external fields
Restoration must reduce externalized cost and repair burdened fields
ΤTime reveals return of externalized debt
ΘPrevents overclaiming local stability as coherence
ΣDefines the measured basin and excluded cost field
ΨField and affected-node feedback reveals who pays for stability
ΛCompatibility tests whether local stability aligns with whole-field coherence

Coherent operator sequence:

textScroll
Γ(classify stability source) → Θ(local stability humility) → Σ(map measured vs excluded cost field) → Au/FI(trace externalized burden) → Ψ(validate burdened nodes) → ℛ(reduce externalized cost) → Τ(validate O_local + O_global)

Inverted operator sequence:

textScroll
O_local stable → Φ_local↑ → Cost_externalized↑ → Γ(stability claimed) → Au_export↓ → H_field↑ → Ξ / ι↑ → O_global↓

14. Machine-Readable Summary

yamlScroll
id: "LAW-079"
name: "Local Stability Export Law"
type: "law"
status: "draft"
family:
  - "Basin and Attractor Laws"
summary: "If stability depends on externalization, hidden debt is increasing somewhere."
canonical_statement: "If stability depends on externalization, hidden debt is increasing somewhere."
core_form: "stability depends on externalization ⇒ H↑ somewhere"
expanded_form: "O_local stable ∧ Cost_externalized↑ ⇒ H_field↑ ∧ O_global↓"
diagnostic_form: "local stability + external burden + low export auditability ⇒ stability-export pattern"
restoration_valid_contrast: "local stability persists after cost internalization ⇒ stability more likely coherent"
variables:
  primary:
    - "O_local"
    - "O_global"
    - "H_field"
    - "H_export"
    - "Cost_externalized"
    - "Au_export"
    - "Φ_local"
    - "ι"
    - "Ξ"
    - "BΣ"
  secondary:
    - "O"
    - "H"
    - "ε"
    - "Au"
    - "R"
    - "R_eff"
    - "K"
    - "σ"
    - "FI"
    - "µᵢ"
    - "Φ"
    - "Λ"
    - "⊗"
    - "Γ"
    - "Π"
    - "ℛ"
    - "Θ"
    - "Σ"
    - "Ψ"
    - "Τ"
    - "L"
diagnostics:
  - "Local Stability Export"
  - "Externalized Cost"
  - "Hidden Debt Export"
  - "Local-Global Coherence Gap"
  - "Debt Migration"
  - "Exported Burden"
  - "Effective Auditability"
  - "Observability Distribution"
  - "Exit Cost"
  - "Resource Gatekeeping"
  - "Legitimacy Baseline"
  - "Coherence Trajectory"
  - "Recurrence"
failure_modes:
  - "Local Stability Export"
  - "Externalized Cost Stability"
  - "Hidden Debt Export"
  - "Pseudo-Coherent Basin"
  - "Incoherence Displacement"
  - "Debt Migration"
  - "Silent Extraction"
  - "Exit Cost Lock"
  - "Normalization Shield"
  - "Legitimacy Debt"
  - "Suppressed Potential"
  - "Pseudo-Restoration"
  - "Delayed Collapse"
restoration_arcs:
  - "Local Stability Audit"
  - "Export Channel Mapping"
  - "Debt Export Reversal"
  - "Hidden Debt Reduction"
  - "Auditability Restoration"
  - "Observability Redistribution"
  - "Boundary Reconstitution"
  - "Slack Regeneration"
  - "Exit Cost Reduction"
  - "Resource Flow Redesign"
  - "Higher-Order Attractor Formation"
  - "Basin Supersession"
  - "Temporal Validation"
related_laws:
  - "LAW-003"
  - "LAW-004"
  - "LAW-005"
  - "LAW-006"
  - "LAW-008"
  - "LAW-010"
  - "LAW-011"
  - "LAW-013"
  - "LAW-015"
  - "LAW-017"
  - "LAW-030"
  - "LAW-031"
  - "LAW-032"
  - "LAW-053"
  - "LAW-058"
  - "LAW-064"
  - "LAW-065"
  - "LAW-072"
  - "LAW-073"
  - "LAW-077"
  - "LAW-078"
  - "LAW-080"
  - "LAW-081"
  - "LAW-082"
  - "LAW-083"
  - "LAW-084"
  - "LAW-102"
  - "LAW-119"
  - "LAW-148"
  - "LAW-149"
  - "LAW-150"
  - "LAW-171"
related_invariants:
  - "INV-001"
  - "INV-004"
  - "INV-006"
  - "INV-080"
operator_sequence:
  coherent:
    - "Γ classify stability source"
    - "Θ local stability humility"
    - "Σ map measured vs excluded cost field"
    - "Au/FI trace externalized burden"
    - "Ψ validate burdened nodes"
    - "ℛ reduce externalized cost"
    - "Τ validate O_local + O_global"
  inverted:
    - "O_local stable"
    - "Φ_local↑"
    - "Cost_externalized↑"
    - "Γ stability claimed"
    - "Au_export↓"
    - "H_field↑"
    - "Ξ / ι↑"
    - "O_global↓"
aliases:
  - "Local Stability Export Law"
  - "Externalized Stability Law"
  - "Stability Through Externalization Law"
  - "Externalized Cost Stability Law"
  - "Local Stability Debt Law"
  - "Exported Stability Debt Law"
  - "Stability Paid Elsewhere Law"
deduplication_note: "Compact local-stability export discriminator. LAW-077 defines pseudo-coherent basins broadly, LAW-078 specifies export channels and signatures, LAW-080 explains why basin escape becomes costly, LAW-081 defines the need for a higher-order attractor, and LAW-082 defines the restoration method for pseudo-coherent basins."
source: "content/archive/laws/technical.md"

15. Compact Card Version

LAW-079 — Local Stability Export Law

If stability depends on externalization, hidden debt is increasing somewhere.

Core form:

textScroll
stability depends on externalization ⇒ H↑ somewhere

Expanded form:

textScroll
O_local stable ∧ Cost_externalized↑ ⇒ H_field↑ ∧ O_global↓

Plain meaning:

A system may appear stable because the cost of its stability is paid elsewhere. When local order depends on exporting burden, risk, labor, damage, confusion, instability, or future cost outside the measured basin, the system is not fully coherent. It is stable through externalization.

Diagnostic form:

textScroll
local stability + external burden + low export auditability ⇒ stability-export pattern

Restoration-valid contrast:

textScroll
local stability persists after cost internalization ⇒ stability more likely coherent

Primary variables:

O_local, O_global, H_field, H_export, Cost_externalized, Au_export, Φ_local, ι, Ξ, , K, σ, FI, µᵢ, Γ, Π, , Θ, Σ, Ψ, Τ, L

Diagnostic signature:

Local stability and success proxies improve while externalized cost rises, export auditability decreases, burdened nodes lose slack, exit cost increases, and whole-field coherence declines.

Failure risk:

Local stability export, externalized cost stability, hidden debt export, pseudo-coherent basin, incoherence displacement, debt migration, silent extraction, exit cost lock, normalization shield, legitimacy debt, suppressed potential, pseudo-restoration, delayed collapse.

Restoration priority:

Map the measured basin and excluded cost field, restore export auditability, trace burden destinations, internalize or repair externalized cost, redistribute restoration capacity, reduce exit costs, and time-validate that both local and global coherence hold.