Solution composition
Versions and Compatibility
On this page
The solution uses the effority.solution.technology-consulting-delivery@1.x release line. Documentation version 1.0 describes the composition and contracts; it does not imply every installed package has an identical version number.
Three distinct records
| Record | What it identifies |
|---|---|
| Solution manifest | Required and optional package membership, compatible ranges, sector defaults and activation rules |
| Package release | Publisher identity, provided capabilities, dependencies, schema/migration contracts, signatures and qualification evidence |
| Environment lock | Exact resolved package, model/runtime and overlay versions for one deployment |
Compatibility review
Check dependency ranges, capability contracts, schema changes, interface-slot collisions, permissions and model/runtime profiles. A new package can enrich a compatible host without replacing its original release. Major behavioral or schema changes require explicit migration and dependent-package qualification.
Upgrade and recovery
Compare the current and proposed locks, run regression and migration tests, qualify in Staging and record the approved Production change. Rollback is conditional on compatible data and retained artifacts. Irreversible migrations require tested recovery; completed external effects need compensation or remediation.
Package references
The composition inventory links each package's upgrade guidance and technical reference. A release does not silently rewrite historical findings, report versions or source evidence.