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

Use this when critical admin or developer tools fail only after the OS moves ahead of the assumptions built into older packages. 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.

• macOS assumptions are often changed indirectly by updates, policy, hardware changes, or cleanup work that looked harmless at the time.
• Rosetta 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.
• Migration assumptions are often changed indirectly by updates, policy, hardware changes, or cleanup work that looked harmless at the time.