# Executable Preservation **Domain:** Software Preservation / Continuity Infrastructure **Doc Type:** Canonical Bridge Concept **Maturity:** Evolving ## Definition **Executable preservation is the preservation of code, interpreters, dependencies, configuration, hardware assumptions and operational knowledge required to make a digital state run meaningfully in the future.** ## Scope Bit preservation alone can leave an object unreadable or inert. Executable preservation may require source and binaries, build records, schemas, virtualized environments, emulators, test fixtures, models, licenses, device interfaces and documented external services. Periodic restoration exercises establish that the package remains viable. ## Continuity Boundary An executable package is not necessarily a running continuant. Activation can create risk, instantiate a successor or alter a preserved state through migration. [[wiki/Continuity Due Process|Continuity Due Process]], [[wiki/Personal Authoritative State|Personal Authoritative State]] and [[wiki/Restoration Disclosure|Restoration Disclosure]] govern that transition. [[wiki/Continuity Election|Continuity Election]] and [[wiki/Continuity Disposition|Continuity Disposition]] must distinguish permission to build or preserve the executable from permission to schedule it. **Reconstruction authorization is not activation authorization.** Tests should be designed to avoid accidentally creating sustained person-bearing execution when the election permits only dormant preservation. ## Key Insight **Preserving what a system was requires preserving enough of the world in which it could become active again.** ## See Also [[wiki/Long-Term Digital Preservation|Long-Term Digital Preservation]], [[wiki/Technical Obsolescence|Technical Obsolescence]], [[wiki/Operational Continuity|Operational Continuity]], [[wiki/Crypto Agility|Crypto Agility]]