# Single-File Portability **Domain:** Distribution / Deployment **Doc Type:** Canonical Concept Node **Maturity:** Artifact-Derived **Related:** [[wiki/Generated Combined Distribution|Generated Combined Distribution]], [[wiki/Generated Packaging|Generated Packaging]], [[wiki/Portability|Portability]] --- ## Definition **Single-file portability is the ability to deploy a library or data product as one generated file when directory depth, file count, installation control, or package infrastructure is constrained.** It is a distribution geometry, not a requirement that development occur in a monolith. ## Shazam Context Shazam remained modular during development while its build system emitted `shazam-complete.pm` for hosts where a single importable file was more practical. The same principle later appeared in self-contained applications and portable data bundles. ## Key Insight **Modular authorship and single-file deployment are compatible when the combined form is generated.** ## See Also [[projects/Shazam - A Portable Perl Capability Library|Shazam]], [[wiki/Folder-Native Architecture|Folder-Native Architecture]], [[wiki/Generated Packaging|Generated Packaging]], [[wiki/Technical Terms|Technical Terms]]