Configuration lifecycle

Velox configuration is a connected graph of modules, not a set of isolated files. A safe change moves from design and test through dependency review, controlled packaging, target-context import, comparison, production verification and recoverable evidence.

Lifecycle

1. Identify the changed module and its dependencies and relationships.
2. Complete representative test execution and record the approved scope.
3. Export and package a controlled .CFG artefact, or use the context-to-context promotion command.
4. Import and validate in the intended target context.
5. Compare and verify structure, environment values and behaviour.
6. Promote configuration during an approved change window.
7. Retain evidence and be ready to roll back and recover.

Configuration promotion does not deploy Velox binaries, database schema or external-system changes. Coordinate those through the relevant installation/upgrade and external change processes.

Use configuration templates for the product mechanics and governance, approvals and evidence for the minimum change record.