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

Use this when users authenticate successfully and Finder or automation workflows cannot restore the expected mapped paths. 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.
• File Shares assumptions are often changed indirectly by updates, policy, hardware changes, or cleanup work that looked harmless at the time.
• Extensions assumptions are often changed indirectly by updates, policy, hardware changes, or cleanup work that looked harmless at the time.
• Networking assumptions are often changed indirectly by updates, policy, hardware changes, or cleanup work that looked harmless at the time.