Exercise 2: Why Projects Survive an Employee Leaving — Possible Solution
====================================================================

Google's own real, documented organizational principle is explicit:
resources don't belong to the individual employee who created them -
they belong to the Organization itself. A Project's own real
ownership was never actually tied to any single person's account in
the first place, even though that person may have been the one who
originally created it.

Because of this real design choice, when an employee who created
several Projects leaves the company, those Projects and everything
inside them remain genuinely intact and under the Organization's own
continued ownership - there's no dependency on that specific
individual's own account remaining active for the Projects to keep
functioning or for administrators to retain access to them.

ANSWER: These Projects aren't at risk of being lost or orphaned
because GCP's real hierarchy was deliberately designed so that
Projects belong to the Organization, not to the individual who
created them - the departing employee's own account being disabled or
removed has no real bearing on the Project's own continued existence,
ownership, or accessibility to other authorized administrators within
the Organization.

WHY THIS WORKS AS AN ANSWER
------------------------------
This correctly cites the chapter's own explicit, real documented
principle as the reason, rather than assuming Projects would somehow
"just work out," and explains the real, practical consequence
(continuity through personnel changes) the principle was specifically
designed to guarantee.