Recovery validation
Resource categories
| Target category | Discovery | Controlled validation boundary |
|---|---|---|
| Kubernetes Deployment or StatefulSet | Yes | Pod deletion, scaling, and supported placement scenarios with safeguards |
| Managed compute group | Integration dependent | Instance recreation while preserving configured group capacity |
| Standalone virtual machine | Integration dependent | Posture and associated backup/restore visibility; no general automatic recovery claim |
| High-availability managed database | Integration dependent | Approved failover only when the feature and explicit safety gate are enabled |
A discovered target is not automatically safe or eligible to mutate. Exact support depends on the cloud integration and release; confirm the intended resource types before purchase.
Execution workflow
- Select the enrolled cloud scope and resource category.
- Select the exact target and confirm its identity.
- Choose Assessment or Objective validation.
- Review the planned action and run a Dry run.
- Resolve preflight warnings.
- Execute during an approved window.
- Observe recovery until the configured timeout.
- Review the result and evidence in History.
Safety controls
- Protected namespaces are refused.
- Kubernetes execution is restricted to the configured home cluster unless the installed integration explicitly supports another execution path.
- A single-ready-replica target surfaces a downtime warning and requires explicit confirmation.
- Per-target leases prevent simultaneous tests against the same target.
- The controller limits independent concurrent runs.
- Destructive or provider failover actions require explicit feature and safety gates.
- Cleanup paths attempt to restore supported scale and node state after a test.
- Entitlement scope, feature, and execution limits are enforced before mutation.
Reading results
- MEASURED — Assessment recorded observed recovery. This is not a compliance PASS.
- PASS — Objective validation met all configured targets.
- FAIL — An approved objective was missed or an expected recovery condition was not met.
- BLOCKED/REJECTED — A safeguard, entitlement rule, unsupported configuration, or preflight check prevented execution.
- ERROR — The run could not complete because of an operational or provider error. Investigate before repeating.
Preserve the run ID, target identity, timestamps, measurements, evidence URI, and digest with the review record.