Package Declaration (YAML)

Documentation status: reference — see Maturity and evidence.

A package groups application artifacts that evolve and are loaded together: manifests, models, services, or other resources published by that package.

Goals

• define a modularity boundary;
• identify items to load;
• make dependencies visible;
• support versioning, distribution, and reuse;
• limit implicit references between modules.

Rules

Conceptual identifiers remain stable independently from the physical file name. Package dependencies should be explicit and avoid uncontrolled cycles.

A package must not become an arbitrary container for environment configuration. Deployment-specific secrets and endpoints stay outside the reusable model.

Loading

Validate the package and its manifests before activating services or views. This progression makes resolution failures easier to diagnose.