SYSE.38:4.2 - Reduce impact within a known boundary

Identify the safest useful mitigation under the actual permission and current state. It may restrict new work, preserve an old serving path, isolate a failed component or use an already qualified alternative. State what remains unavailable or degraded.

Before reattempting a state-changing operation, determine whether it took effect. Query the original attempt or target where possible. If observation is unavailable and repetition could duplicate or corrupt effects, stop that repetition and return the uncertainty for the appropriate assistance.

Use SYSE.34 for uncertain data effects and SYSE.41 for partial deployment state. A restarted process does not prove restored information. A proposed fallback whose capacity, compatibility or authority is unknown is not yet a recovery path.