# Persistence Mechanism A persistence mechanism causes code, configuration, access, or authority to survive reboot, logout, reinstall, migration, credential change, or another recovery action. ## Classes Examples include startup services, scheduled tasks, browser extensions, account recovery channels, MDM enrollment, boot modifications, protected-system changes, cloud automation, and firmware state. ## Evidentiary rule Persistence must be named by layer. A recurring symptom does not establish firmware persistence, and a startup artifact does not establish actor identity. Record mechanism, resident authority, durability, trigger, provenance, and revocation path separately. ## Relationships [[Foundational Persistence]] · [[Persistent Identifier]] · [[Resident Authority]] · [[Recovery Topology]].