Exercise 3: SIP and the Broken "Root Can Do Anything" Assumption — Possible Solution
====================================================================

THE ASSUMPTION BEING REVISED
------------------------------
Per this chapter, every Unix system this course has touched since Chapter 1 - including macOS's own BSD heritage and the sudo-gated overrides in Chapters 5 and 6 - has relied on the unstated assumption that root can do anything: full, unrestricted power over the entire filesystem once root privilege is obtained, by any means.

HOW SIP BREAKS IT
------------------------------
System Integrity Protection restricts even a fully root-privileged process from modifying protected system locations - specifically /System, /bin, /sbin, and most of /usr (excluding /usr/local, which is exactly why Homebrew's own default install location was never affected). This holds regardless of how that root access was obtained, meaning root privilege alone is no longer sufficient to touch those specific protected paths - a genuine, deliberate exception to the traditional Unix rule.

THE ONE WAY SIP CAN ACTUALLY BE DISABLED
------------------------------
SIP cannot be disabled from within a normal running macOS session at all. It requires booting into macOS Recovery and running `csrutil disable` from there - a deliberately inconvenient, out-of-band process rather than a simple Terminal command available during everyday use.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly names the "root can do anything" Unix assumption as the one being revised, explains specifically which protected paths SIP restricts even root from touching, and correctly identifies booting into Recovery and running csrutil disable as the only way to actually turn it off.