INV-079 — Tolerance Is Stack-Dependent

1. Definition

Tolerance is not a fixed property of a living system. It is stack-dependent.

Tolerance is the capacity of a system to receive, process, absorb, metabolize, integrate, or recover from a stimulus without disproportionate destabilization.

A living system’s tolerance depends on the full stack of current conditions:

baseline reserve
current load
sleep / recovery state
nutrition / energy state
inflammation burden
immune state
nervous-system state
boundary integrity
prior exposures
recurrence memory
environmental context
timing
dose
rate of change
meaning / agency conditions
repair capacity

Therefore:

Tolerance is stack-dependent.

A stimulus tolerated under one stack may become intolerable under another.

The stimulus did not necessarily change.

The stack changed.

2. Purpose

This invariant prevents UTS from treating tolerance as an intrinsic, static, moral, or identity-based property.

Systems often say:

• “They tolerate this.”
• “They cannot tolerate this.”
• “This food is bad.”
• “This intervention works.”
• “This workload is fine.”
• “This person is resilient.”
• “This dose is safe.”
• “This stressor is harmless.”
• “This environment is acceptable.”
• “This relationship is tolerable.”
• “This protocol is validated.”

But tolerance changes with stack state.

The false assumption is:

Tolerance is fixed.

The UTS correction is:

Tolerance emerges from the current stack.

This matters because a system may appear intolerant when it is actually overloaded, depleted, inflamed, poorly resourced, boundary-stressed, under-recovered, or carrying unresolved recurrence.

Likewise, a system may tolerate something temporarily by spending reserve, then collapse later.

Tolerance must therefore be interpreted dynamically, not as essence.

3. Constraint Statement

Canonical Form

Tolerance is stack-dependent.

Expanded Form

A living system’s tolerance to food, stress, exertion, medication, environment,
social contact, information, symbolic load, intervention, or relational coupling
depends on the current stack of reserve, load, boundary integrity, timing,
dose, recurrence memory, environmental support, meaning conditions, and
restoration capacity.

Minimal Expression

Tolerance depends on stack state.

Biological Form

The same input can be coherent or incoherent depending on reserve, timing, dose, and burden.

Recovery Form

Tolerance should be rebuilt by restoring the stack, not by forcing exposure alone.

Scaling Form

Challenge may increase only when the tolerance stack can absorb it.

Medical Form

Intolerance is a signal about system-stack conditions, not necessarily a permanent identity.

CMS / Meaning Form

Meaning and symbolic load are tolerated according to embodied capacity, boundary integrity, and integration state.

Economy Form

Workload tolerance depends on biological reserve, social support, slack, repair capacity, and meaning integrity.

4. Structural Logic

Tolerance is not located only in the stimulus.

Tolerance is produced at the interface between:

input
system state
membrane condition
memory
environment
repair capacity
timing
dose
meaning

The same input may produce different outcomes depending on stack state.

Example:

exercise after good sleep, adequate food, and low stress
        ≠
exercise after poor sleep, inflammation, high stress, and low reserve

The input may be identical.

The stack is not.

The incoherent interpretation sequence:

input causes reaction
        ↓
input is labeled bad or system is labeled weak
        ↓
stack conditions are ignored
        ↓
forcing or avoidance becomes rigid
        ↓
tolerance does not rebuild
        ↓
recurrence continues

The coherent interpretation sequence:

input causes reaction
        ↓
stack conditions are mapped
        ↓
reserve, load, boundary, timing, and dose are assessed
        ↓
repair capacity is rebuilt
        ↓
input is reintroduced gradually if appropriate
        ↓
ring-down and recurrence are tracked
        ↓
tolerance improves or limits are clarified

Core insight:

Tolerance is an emergent property of the whole stack.

The question is not only:

Can this system tolerate X?

The better question is:

Under what stack conditions can this system tolerate X, and what stack changes make tolerance more or less likely?

5. State-Vector Impact

Protected State Variables

O   — coherence
R   — restoration capacity
BΣ  — boundary integrity
K   — compatibility between input and system stack
Au  — auditability / signal interpretation
µᵢ  — meaning / agent integrity
H   — hidden biological or systemic debt

Primary Risk Variables

ε   — visible intolerance, flare, overload, crash, conflict, symptom, refusal
ι   — inversion when intolerance is mistaken for essence or tolerance is mistaken for recovery
Φ   — performance, exposure success, dose tolerance, productivity, compliance, short-term output

Healthy Tolerance Pattern

reserve↑
load appropriate
BΣ↑
R↑
dose paced
ring-down improves
recurrence↓
K↑
O↑

Violation Pattern

challenge↑
reserve↓
load↑
BΣ↓
R insufficient
ring-down worsens
ε↑
H↑
ι↑
O↓

Tolerance-Essence Inversion

reaction occurs
        ↓
system is labeled intolerant / fragile / noncompliant
        ↓
stack ignored
        ↓
H↑

The key inversion:

stack-state reaction is mistaken for fixed identity.

False-Tolerance Pattern

input tolerated briefly
reserve consumed
delayed crash occurs
tolerance was misread

Tolerance must be validated by ring-down and recurrence, not immediate survival.

6. U-Layer Localization

Primary Layer

U1 — Power / Budgets

Tolerance depends heavily on reserve: energy, nutrients, sleep, time, repair capacity, immune resources, attention, and slack.

Boundary Layer

U2 — Configuration / Boundaries

Tolerance depends on membrane and boundary function: gut barrier, immune discrimination, nervous-system thresholds, relational boundaries, workload boundaries, and consent boundaries.

Execution Layer

U3 — Execution

Tolerance appears through real-time response: digestion, movement, immune activation, pain, fatigue, behavior, performance, and output.

Classification Layer

U4 — Classification / Metrics

Tolerance is often misclassified through labels: allergy, sensitivity, resilience, weakness, noncompliance, fitness, productivity, stable, unstable.

Coordination Layer

U5 — Coordination / Time

Tolerance is temporal. Timing, pacing, dose interval, recovery time, and delayed reactions determine validity.

Coherence Field Layer

U6 — Coherence Field

Meaning, agency, safety, trust, and interpretation affect tolerance. A stimulus may become less tolerable when it is forced, threatening, confusing, or unchosen.

Memory Layer

U7 — Memory / Recurrence

Prior exposure, sensitization, immune memory, trauma load, skill memory, recurrence history, and adaptation shape current tolerance.

Environment Layer

U8 — Environment / Forcing

Temperature, pollution, pathogens, social stress, work demand, food environment, financial stress, and symbolic field shape tolerance.

Common Failure Pattern

U8 load rises
        ↓
U1 reserve declines
        ↓
U2 boundaries weaken
        ↓
U7 recurrence memory sensitizes
        ↓
U3 reaction occurs
        ↓
U4 label assigned
        ↓
stack ignored
        ↓
H↑

Common Misdiagnosis

Tolerance failure is often misdiagnosed as:

• weakness
• noncompliance
• laziness
• fragility
• overreaction
• allergy only
• sensitivity as identity
• poor discipline
• lack of resilience
• treatment failure only
• bad attitude
• intolerance as permanent
• symptom exaggeration

The deeper issue may be:

The tolerance stack is overloaded, depleted, sensitized, or mis-sequenced.

7. Violation Signatures

7.1 Same Input, Different Response

The system tolerates an input one day and reacts another day.

input same
stack different
response different

This signals stack dependence, not inconsistency.

7.2 Intolerance During Low Reserve

Symptoms or reactions appear when sleep, nutrition, recovery, or repair reserve is low.

reserve↓
input tolerance↓
ε↑

The input may be only one part of the failure.

7.3 Dose-Rate Mismatch

The system might tolerate a small dose or slow increase but react to rapid or large exposure.

dose / rate↑
R insufficient
reaction↑

Tolerance depends on pacing.

7.4 Boundary-Stress Intolerance

The system reacts because membranes or boundaries are already stressed.

BΣ↓
input burden↑
ε↑

Examples include gut permeability, immune sensitization, relational boundary overload, or data-boundary stress.

7.5 Forced Exposure Without Stack Repair

A system is pushed into exposure, training, social contact, workload, or intervention without reserve rebuild.

exposure↑
stack repair↓
recurrence↑

Exposure alone does not rebuild tolerance.

7.6 Avoidance Becomes Permanent Identity

The system avoids an input long-term and labels it impossible without testing whether the stack can be repaired.

avoidance↑
reintroduction untested
identity binding↑

Avoidance may be useful temporarily, but it should not become essence without validation.

7.7 False Tolerance Through Compensation

The system appears to tolerate load but compensates through stress activation, suppression, dissociation, over-control, or reserve consumption.

visible tolerance↑
hidden cost↑
delayed ε↑

Tolerance must be checked over time.

7.8 Meaning Conditions Alter Tolerance

A stimulus is tolerated when chosen, understood, or meaningful, but not when coerced, confusing, or unsafe.

same input
meaning / agency different
tolerance different

Meaning is part of the stack.

7.9 Economic Load Misread as Personal Tolerance

A person or group appears unable to tolerate work, change, learning, or adaptation because economic slack and repair capacity are gone.

economic slack↓
adaptation tolerance↓

This is not personal failure.

7.10 AI / System Tolerance Misread

A technical or AI system handles load in tests but fails under production context because stack conditions differ.

test tolerance↑
production stack different
failure↑

Tolerance is stack-dependent across engineered systems too, by analogy.

8. Related Failure Modes

Primary related failure modes:

• Tolerance Stack Collapse
• Tolerance-Essence Inversion
• False Tolerance
• Dose-Rate Mismatch
• Boundary-Stress Intolerance
• Forced Exposure Failure
• Avoidance Identity Binding
• Compensation Masking
• Reserve-Dependent Intolerance
• Meaning-Condition Intolerance
• Recurrence Sensitization
• Overload Misread as Weakness
• Economic Adaptation Burden
• Performance-Health Inversion
• Intervention Overload
• Perturbation Intolerance
• Biological Hidden Debt
• Protocol Mismatch
• Recovery Theater
• Boundary Regulation Failure
• Hidden Debt Accumulation
• Medical Reductionism

9. Related Restoration Arcs

Primary restoration arcs:

• Tolerance Stack Mapping
• Reserve Rebuild
• Load Reduction
• Boundary Regulation Repair
• Dose / Rate Recalibration
• Gradual Reintroduction
• Perturbation Tolerance Rebuild
• Ring-Down Tracking
• Recurrence Desensitization
• Meaning / Agency Restoration
• Avoidance Reassessment
• False Tolerance Audit
• Environmental Re-Coupling
• Recovery Capacity Scaling
• Protocol Recalibration
• Economic Slack Restoration
• Relational Boundary Repair
• Signal Reinterpretation
• Temporal Validation
• Whole-Stack Integration

Restoration Requirement

Tolerance repair requires stack repair, not force alone.

Minimal sequence:

Identify intolerance or tolerance failure
        ↓
Map stack state: reserve, load, boundary, timing, dose, memory, environment
        ↓
Reduce excessive load
        ↓
Rebuild repair reserve
        ↓
Restore boundary regulation
        ↓
Reintroduce challenge gradually if appropriate
        ↓
Track ring-down and recurrence
        ↓
Adjust dose / timing / environment
        ↓
Validate tolerance over time

10. Domain Expressions

Biology / Medicine

Biological tolerance applies to:

food
exercise
sleep variation
medication
supplements
infection exposure
temperature
light
sound
social load
cognitive demand
stress
environmental chemicals

A biological system may tolerate an input when reserve is high and react when reserve is low.

Medicine should avoid labeling intolerance as essence too early.

Better interpretation:

This system currently cannot tolerate this input under this stack.

not:

This system is permanently intolerant.

AI / Medical AI

Medical AI should not infer permanent intolerance from isolated reactions.

It should track:

• dose
• timing
• reserve state
• sleep
• stress
• co-exposures
• recurrence
• ring-down
• prior sensitization
• boundary integrity
• environmental context

AI should help map tolerance stacks, not produce rigid labels too early.

AI Governance

AI governance should recognize stack-dependent tolerance in users and systems.

Examples:

users tolerate notifications differently under stress
workers tolerate automation differently when transition support exists
communities tolerate policy changes differently when repair pathways exist
AI systems tolerate load differently in test versus deployment

Governance must evaluate context, not only static capability.

Security

Security tolerance includes how much friction, monitoring, restriction, or verification a system can absorb without degrading function, trust, or agency.

A user may tolerate security friction when the reason is clear and appeal exists.

The same friction becomes intolerable when opaque, punitive, or constant.

security friction tolerance = stack-dependent

Economy

Economic tolerance includes how much change, price shock, labor demand, debt, automation, or uncertainty households, workers, suppliers, and communities can absorb.

A policy may be tolerable when slack exists.

The same policy becomes destabilizing when reserve is depleted.

Economic adaptation requires slack.

adaptation tolerance depends on economic stack

CMS / Meaning

Meaning tolerance includes how much truth, symbolism, grief, complexity, initiation, contradiction, or identity change a person or community can integrate.

A symbolic truth may be tolerable when there is:

trust
capacity
context
support
timing
agency
boundary
repair path

and intolerable when forced, decontextualized, or unsupported.

Principles / Archetypes

Principles and archetypes have tolerance conditions.

Examples:

truth requires integration capacity
justice requires repair capacity
love requires boundary capacity
sovereignty requires support and exit
wisdom requires timing
protection requires discernment

An archetype may be tolerable in small doses and overwhelming if identity-bound.

Tolerance to archetypal intensity depends on stack.

Relationships / Couplings

Relational tolerance depends on the stack.

A person may tolerate closeness, conflict, honesty, distance, vulnerability, or change differently depending on:

sleep
stress
trust
repair history
boundary clarity
economic load
prior recurrence
meaning
support

A relationship should not treat variable tolerance as inconsistency or bad faith without stack mapping.

Project / Knowledge Systems

Knowledge systems have tolerance too.

A project may tolerate:

complexity
new concepts
thread length
classification load
cross-link density
technical depth
review burden

only if the stack includes:

clear templates
handoffs
glossaries
review cycles
versioning
memory support
restoration capacity

If the project stack is overloaded, even good content becomes intolerable.

11. Scaling Behavior

As load scales, tolerance depends more strongly on the stack.

Scale increases:

total burden
complexity
co-exposures
recovery demand
boundary stress
memory sensitization
environmental interaction
hidden debt

Therefore:

Load↑ ⇒ tolerance stack requirements↑

Scaling Risk Pattern

challenge↑
stack unchanged
tolerance assumed
reaction↑
H↑

Valid Scaling Pattern

challenge↑
reserve↑
boundary regulation↑
dose paced
ring-down tracked
tolerance rebuilt
O↑

High-Risk Tolerance Claims

High-risk tolerance claims include:

• return to work
• return to training
• medication tolerance
• food tolerance
• stress tolerance
• social tolerance
• AI deployment load tolerance
• policy tolerance
• security friction tolerance
• economic adaptation tolerance
• symbolic initiation tolerance

These require stack mapping.

Relation to INV-077

INV-077 states:

Biological recovery requires ring-down and perturbation tolerance.

INV-079 adds:

Perturbation tolerance itself depends on the whole stack.

Together:

Recovery requires dynamic tolerance, and tolerance requires stack coherence.

12. Canonical Examples

Example 1 — Food Tolerance Changes

A person tolerates a food when rested but reacts during stress and poor sleep.

food same
stack different
reaction different

The food may not be the sole cause.

The stack changed.

Example 2 — Exercise Tolerance

A workout is fine at low stress but causes a crash after sleep debt and workload.

training input same
reserve↓
ε↑

Tolerance was reserve-dependent.

Example 3 — Medication Tolerance

A medication is tolerated at low dose and slow titration but not at rapid increase.

dose rate↑
ring-down insufficient
reaction↑

Pacing matters.

Example 4 — Workplace Adaptation

A team tolerates change when staffed and supported, but not after burnout and layoffs.

change demand↑
slack↓
adaptation tolerance↓

The team is not resistant by essence.

The stack is depleted.

Example 5 — Relationship Conversation

A difficult conversation is tolerated after rest and repair but escalates during overload.

topic same
relational stack different
ring-down different

Timing matters.

Example 6 — Symbolic Truth

A symbolic insight is helpful in a supported context but destabilizing when delivered abruptly.

truth same
container different
tolerance different

Meaning tolerance is stack-dependent.

Example 7 — AI System Under Production Load

An AI workflow works in testing but fails under real users, higher variance, adversarial prompts, and tool latency.

capability same
deployment stack different
failure↑

System tolerance was stack-dependent.

13. Anti-Patterns

Anti-Pattern 1 — “They Cannot Tolerate It”

Better:

They cannot tolerate it under the current stack.

Anti-Pattern 2 — “They Tolerated It Before”

Past tolerance does not prove current tolerance.

Anti-Pattern 3 — “Exposure Builds Tolerance”

Only if reserve, pacing, boundary, and repair conditions are right.

Anti-Pattern 4 — “Avoidance Means Permanent Intolerance”

Avoidance may be temporary stabilization.

Anti-Pattern 5 — “Reaction Means the Input Is Always Bad”

Reaction means the input-stack relation failed.

Anti-Pattern 6 — “No Immediate Reaction Means Tolerated”

Delayed reactions matter.

Anti-Pattern 7 — “Tolerance Means Recovery”

Tolerance may be compensatory if hidden cost is high.

Anti-Pattern 8 — “Stress Tolerance Is Character”

Stress tolerance depends on reserve, support, boundaries, and history.

Anti-Pattern 9 — “Protocol Dose Applies Universally”

Dose tolerance depends on stack.

Anti-Pattern 10 — “System Passed Test, So It Will Tolerate Deployment”

Test stack may differ from production stack.

14. Related Laws

This invariant connects strongly to:

• Tolerance Stack Law
• Biological Reserve Law
• Perturbation Tolerance Law
• Ring-Down Validation Law
• Living Systems as Adaptive Coherence Law
• Boundary Integrity Law
• Wisdom Requires Timing and Scale Law
• Capacity Before Demand Law
• Slack Sovereignty Law
• Symptom Is Signal Law
• Performance Is Not Health Law
• Time Validates Law
• Context Determines Expression Law
• Recovery Requires Dynamic Response Law
• O ≠ Φ Law

15. Related Scaling Rules

Related scaling rules:

• Challenge Must Scale With Reserve
• Dose Must Scale With Repair Capacity
• Exposure Must Follow Boundary Repair
• Reintroduction Must Be Gradual and Reversible
• Tolerance Claims Must Be Time-Validated
• Current Stack Must Be Mapped Before Load Increase
• Past Tolerance Must Not Be Treated as Current Tolerance
• Delayed Response Must Count in Tolerance Assessment
• Meaning Load Must Scale With Integration Capacity
• Economic Change Must Scale With Slack
• Security Friction Must Scale With Trust and Appeal
• Deployment Load Must Match Production Stack
• When Stack Cannot Support Input, Input Scope Must Shrink

16. Related Gates

Relevant gates:

• Tolerance Stack Gate
• Biological Reserve Gate
• Perturbation Tolerance Gate
• Ring-Down Gate
• Dose / Rate Gate
• Reintroduction Gate
• Boundary Regulation Gate
• Load Gate
• Recovery Validation Gate
• Intervention Load Gate
• Economic Slack Gate
• Relational Timing Gate
• Meaning Integration Gate
• AI Deployment Stack Gate
• Security Friction Gate
• Temporal Validation Gate
• High Risk Gate
• Restoration Capacity Gate
• Wisdom Timing Gate

Gate Logic

A tolerance claim fails the tolerance stack gate when:

current reserve is insufficient

or when:

load is increased without ring-down validation

or when:

past tolerance is treated as current tolerance

or when:

delayed reaction is ignored

or when:

boundary stress is unresolved

or when:

dose / rate exceeds repair capacity

or when:

meaning, agency, or consent conditions are ignored

Gate failure returns:

∅

Meaning:

input, load, dose, exposure, deployment, or coupling is not currently admissible under stack conditions

The coherent response may be:

reduce load
restore reserve
repair boundaries
slow dose / rate
improve environment
restore agency
track ring-down
test gradually
validate over time

17. Related Operators

18. Machine-Readable Summary

id: UTS-INV-079
name: Tolerance Is Stack-Dependent
registry: UTS Invariants Registry
category: Biology Invariant / Tolerance Invariant / Stack Invariant / Adaptive Capacity Invariant
status: Draft-Integrated
version: 0.1

definition: >
  Tolerance is not a fixed property of a living system. It is stack-dependent.
  Tolerance is the capacity of a system to receive, process, absorb, metabolize,
  integrate, or recover from a stimulus without disproportionate destabilization.

constraint: >
  A living system's tolerance to food, stress, exertion, medication,
  environment, social contact, information, symbolic load, intervention, or
  relational coupling depends on the current stack of reserve, load, boundary
  integrity, timing, dose, recurrence memory, environmental support, meaning
  conditions, and restoration capacity.

canonical_form:
  - "Tolerance is stack-dependent"
  - "Tolerance depends on stack state"
  - "The same input can be coherent or incoherent depending on reserve, timing, dose, and burden"
  - "Tolerance is an emergent property of the whole stack"
  - "Stack-state reaction is not essence"
  - "Past tolerance does not prove current tolerance"

protects:
  - tolerance_integrity
  - adaptive_capacity
  - biological_reserve
  - boundary_regulation
  - repair_capacity
  - dose_timing_fit
  - recurrence_reduction
  - meaning_agency_conditions
  - perturbation_tolerance
  - temporal_validation

state_vector_effects_when_preserved:
  O: "stable_or_increasing_because_input_matches_current_capacity"
  H: "decreases_as_tolerance_is_rebuilt_without_overload"
  ε: "intolerance_signals_are_interpreted_as_stack_information"
  ι: "decreases_because_reaction_is_not_misread_as_identity"
  Au: "increases_through_stack_mapping_and_delayed_response_tracking"
  µᵢ: "preserved_because_intolerance_is_not_moralized_or_identity_bound"
  BΣ: "improves_through_boundary_regulation"
  K: "increases_between_input_dose_timing_environment_and_system_capacity"
  R: "increases_through_reserve_rebuild_and_repair_capacity"
  Φ: "performance_dose_success_exposure_success_or_immediate_tolerance_not_misread_as_recovery"

state_vector_effects_when_violated:
  O: "decreases_when_input_exceeds_current_stack_capacity"
  H: "increases_through_overload_delayed_reaction_and_unrepaired_burden"
  ε: "appears_as_flare_crash_symptom_conflict_refusal_or_failure"
  ι: "increases_when_stack_state_is_misread_as_essence_or_fixed_tolerance"
  Au: "decreases_when_stack_conditions_and_delayed_responses_are_ignored"
  µᵢ: "degrades_when_intolerance_is_moralized_or_identity_bound"
  BΣ: "decreases_when_boundary_stress_is_ignored"
  K: "declines_between_input_and_current_system_state"
  R: "overwhelmed_when_dose_or_load_exceeds_repair_capacity"
  Φ: "may_rise_through_immediate_performance_or_apparent_tolerance_while_hidden_cost_rises"

primary_u_layer: U1
boundary_layer: U2
execution_layer: U3
classification_layer: U4
coordination_layer: U5
field_layer: U6
memory_layer: U7
environment_layer: U8

violation_signatures:
  - same_input_different_response
  - intolerance_during_low_reserve
  - dose_rate_mismatch
  - boundary_stress_intolerance
  - forced_exposure_without_stack_repair
  - avoidance_becomes_permanent_identity
  - false_tolerance_through_compensation
  - meaning_conditions_alter_tolerance
  - economic_load_misread_as_personal_tolerance
  - ai_system_tolerance_misread

related_failure_modes:
  - Tolerance Stack Collapse
  - Tolerance Essence Inversion
  - False Tolerance
  - Dose Rate Mismatch
  - Boundary Stress Intolerance
  - Forced Exposure Failure
  - Avoidance Identity Binding
  - Compensation Masking
  - Reserve Dependent Intolerance
  - Meaning Condition Intolerance
  - Recurrence Sensitization
  - Overload Misread As Weakness
  - Economic Adaptation Burden
  - Performance Health Inversion
  - Intervention Overload
  - Perturbation Intolerance
  - Biological Hidden Debt
  - Protocol Mismatch
  - Recovery Theater
  - Boundary Regulation Failure
  - Hidden Debt Accumulation
  - Medical Reductionism

related_restoration_arcs:
  - Tolerance Stack Mapping
  - Reserve Rebuild
  - Load Reduction
  - Boundary Regulation Repair
  - Dose Rate Recalibration
  - Gradual Reintroduction
  - Perturbation Tolerance Rebuild
  - Ring Down Tracking
  - Recurrence Desensitization
  - Meaning Agency Restoration
  - Avoidance Reassessment
  - False Tolerance Audit
  - Environmental Re Coupling
  - Recovery Capacity Scaling
  - Protocol Recalibration
  - Economic Slack Restoration
  - Relational Boundary Repair
  - Signal Reinterpretation
  - Temporal Validation
  - Whole Stack Integration

related_laws:
  - Tolerance Stack Law
  - Biological Reserve Law
  - Perturbation Tolerance Law
  - Ring Down Validation Law
  - Living Systems As Adaptive Coherence Law
  - Boundary Integrity Law
  - Wisdom Requires Timing And Scale Law
  - Capacity Before Demand Law
  - Slack Sovereignty Law
  - Symptom Is Signal Law
  - Performance Is Not Health Law
  - Time Validates Law
  - Context Determines Expression Law
  - Recovery Requires Dynamic Response Law
  - O Not Equal Phi Law

related_scaling_rules:
  - Challenge Must Scale With Reserve
  - Dose Must Scale With Repair Capacity
  - Exposure Must Follow Boundary Repair
  - Reintroduction Must Be Gradual And Reversible
  - Tolerance Claims Must Be Time Validated
  - Current Stack Must Be Mapped Before Load Increase
  - Past Tolerance Must Not Be Treated As Current Tolerance
  - Delayed Response Must Count In Tolerance Assessment
  - Meaning Load Must Scale With Integration Capacity
  - Economic Change Must Scale With Slack
  - Security Friction Must Scale With Trust And Appeal
  - Deployment Load Must Match Production Stack
  - When Stack Cannot Support Input Input Scope Must Shrink

related_gates:
  - Tolerance Stack Gate
  - Biological Reserve Gate
  - Perturbation Tolerance Gate
  - Ring Down Gate
  - Dose Rate Gate
  - Reintroduction Gate
  - Boundary Regulation Gate
  - Load Gate
  - Recovery Validation Gate
  - Intervention Load Gate
  - Economic Slack Gate
  - Relational Timing Gate
  - Meaning Integration Gate
  - AI Deployment Stack Gate
  - Security Friction Gate
  - Temporal Validation Gate
  - High Risk Gate
  - Restoration Capacity Gate
  - Wisdom Timing Gate

19. Compact Canon Statement

UTS-INV-079 states that tolerance is stack-dependent. Tolerance is not a fixed property, identity, or moral trait; it emerges from the current stack of reserve, load, boundary integrity, timing, dose, recurrence memory, environmental support, meaning conditions, and restoration capacity. The same input may be coherent under one stack and destabilizing under another. Past tolerance does not prove current tolerance. Intolerance is a signal about system-stack conditions, not necessarily a permanent essence.

20. Short Reference Version

UTS-INV-079 — Tolerance Is Stack-Dependent

Tolerance depends on stack state.

The same input can be tolerated or not tolerated
depending on:

reserve
load
sleep
nutrition
stress
inflammation
boundary integrity
timing
dose
rate of change
recurrence memory
environment
meaning / agency
repair capacity

Core rule:

Stack-state reaction is not essence.
Past tolerance does not prove current tolerance.
Immediate tolerance does not prove durable tolerance.

Healthy pattern:

reserve↑
load appropriate
BΣ↑
R↑
dose paced
ring-down improves
recurrence↓
K↑
O↑

Violation pattern:

challenge↑
reserve↓
load↑
BΣ↓
R insufficient
ring-down worsens
ε↑
H↑
ι↑
O↓

Tolerance repair requires stack repair,
not force alone.