# Generated Packaging **Domain:** Build Systems / Distribution **Doc Type:** Canonical Concept Node **Maturity:** Artifact-Derived **Related:** [[wiki/Lazy-Loading Facade|Lazy-Loading Facade]], [[wiki/Generated Combined Distribution|Generated Combined Distribution]], [[wiki/Single-File Portability|Single-File Portability]] --- ## Definition **Generated packaging derives one or more consumption forms from an authoritative implementation corpus.** A build process may create façades, combined files, reference documents, manifests, bindings, or host-specific bundles without making any generated artifact the only source of truth. ## Shazam Context Shazam treated one-function modules as the editable capability corpus and generated a lazy-loading namespace, documentation, and a combined distribution. Different hosts could consume different geometries without forcing the library to be maintained in several divergent forms. ## Key Insight **Packaging is a projection of the source architecture, not a competing source architecture.** ## See Also [[wiki/Derived Artifact|Derived Artifact]], [[wiki/Rebuildable Projection|Rebuildable Projection]], [[wiki/Tooling|Tooling]], [[wiki/Technical Terms|Technical Terms]]