Template snapshot isolation and explicit upgrades

Installation behavior

A published artifact is versioned and fingerprinted. Installation resolves an exact version and materializes it into the destination application’s private scope.

Consequences

• Master-template edits do not silently break downstream applications.
• White-label/customer customizations remain private.
• Runtime reads can resolve local application state rather than continuously joining a master template with layered overrides.
• Support can identify the baseline version/fingerprint an installation came from.

Upgrades

Upstream upgrades are explicit events. Stable component identities and baseline history can support a three-way comparison between the old baseline, the customer’s private changes, and the new upstream version. Conflicts should be surfaced rather than overwritten silently.