sub-modules
Override and Quarantine
Govern exceptional action, break-glass use, maintenance holds and safe recovery.
An authorized engineer overrides a non-critical hold while a separate hardware fault forces quarantine. Every exception has a bounded scope, expiry, accountable actor and recovery path.
What changes
An authorized engineer overrides a non-critical hold while a separate hardware fault forces quarantine. Every exception has a bounded scope, expiry, accountable actor and recovery path.
data Viz
data View
section: operating-scene
Operational boundary
- What it does
- Govern exceptional action, break-glass use, maintenance holds and safe recovery.
- What the team gains
- Every exception has a bounded scope, expiry, accountable actor and recovery path.
- What it does not own
- An override cannot weaken a non-overridable controller constraint.
- section
- operational-boundary
Override and Quarantine
action: Govern exceptional action, break-glass use, maintenance holds and safe recovery.
mechanism: An authorized engineer overrides a non-critical hold while a separate hardware fault forces quarantine.
workflow role: An authorized engineer overrides a non-critical hold while a separate hardware fault forces quarantine.
operational outcome: Every exception has a bounded scope, expiry, accountable actor and recovery path.
maturity: specified
evidence: MAXACOR Part 5, §§3.3–3.11.
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
An override cannot weaken a non-overridable controller constraint.