Resilience Is Not Uptime

This article examines resilience as a property of purpose preservation rather than continuous operation. It argues that systems optimized primarily for uptime risk persistent misalignment when conditions change, and that resilience instead requires the capacity for intentional constraint, selective degradation, and refusal of action when continuation would compromise core objectives. The discussion distinguishes resilience from reliability, robustness, and redundancy, and frames interruption not as failure but as a legitimate outcome of controlled design. The treatment is intentionally abstract and domain-agnostic, establishing criteria by which resilient behavior may be evaluated independent of specific implementations.