The platform is up, but one dependency path is not.

Use this when services start failing post-restore because the filesystem labels no longer match the expected policy context. These issues are easy to misread because the operating system still responds while one control path, runtime dependency, or trust assumption is already out of alignment.

The symptom usually appears downstream from the real change.

• Linux assumptions are often changed indirectly by updates, policy, hardware changes, or cleanup work that looked harmless at the time.
• SELinux assumptions are often changed indirectly by updates, policy, hardware changes, or cleanup work that looked harmless at the time.
• Restore assumptions are often changed indirectly by updates, policy, hardware changes, or cleanup work that looked harmless at the time.
• Applications assumptions are often changed indirectly by updates, policy, hardware changes, or cleanup work that looked harmless at the time.