sub-modules
Configuration Drift
Detect when accountable hardware, software or policy no longer matches the approved physical configuration.
A staged software wave changes behavior on one cohort while another remains on the previous build. Operators see which outcome belongs to which configuration and rollout wave.
What changes
A staged software wave changes behavior on one cohort while another remains on the previous build. Operators see which outcome belongs to which configuration and rollout wave.
data Viz
data View
section: operating-scene
Operational boundary
- What it does
- Detect when accountable hardware, software or policy no longer matches the approved physical configuration.
- What the team gains
- Operators see which outcome belongs to which configuration and rollout wave.
- What it does not own
- Build and deployment provenance remain with Haephestus.
- section
- operational-boundary
Configuration Drift
action: Detect when accountable hardware, software or policy no longer matches the approved physical configuration.
mechanism: A staged software wave changes behavior on one cohort while another remains on the previous build.
workflow role: A staged software wave changes behavior on one cohort while another remains on the previous build.
operational outcome: Operators see which outcome belongs to which configuration and rollout wave.
maturity: specified
evidence: MAXACOR Part 3, §§11–15.
Section 1
Operations team
Section 2
Engineering team
Section 1
Qualified physical state
Section 2
Current work context
Section 1
Evidence-bearing operational disposition
Section 1
Build and deployment provenance remain with Haephestus.