Package Install and Update Flow

Use this page to follow the package execution flow after system governance has accepted the lifecycle decision. Installer moves files and records results; it does not redefine addon identity.

Rule

Installer handles package execution. system governance decides lifecycle meaning.

For orientation only, see Installer/Package Install and Update Flow.

Flow

1. Installer accepts the package or governed intake source.
2. Installer stages the package in a temporary workspace.
3. Installer extracts and reads only enough package data for handoff.
4. system governance validates identity, manifest contract, dependencies, compatibility, risks, and collisions.
5. system governance returns an approved lifecycle decision or a block.
6. Installer deploys files only from the system governance-approved contract.
7. Installer reports execution results back to the governed lifecycle path.
8. Installer cleans temporary files according to Installer Cleanup Rules.

Update Rule

An update is valid only when system governance confirms the incoming package belongs to the same addon lineage.

Installer must not classify install versus update by folder name alone.

Failure Rule

No package may continue after an system governance block. No partial success should be represented as completed lifecycle truth.

See Addon Development/Route and Slug Collision Handling and Addon Update vs Clean Install.