Private Backpacks and Shared Scrolls

Explain per-process heaps, message passing, and shared code in a narrative way.

Key ideas

Each gnome has its own backpack (heap).

Messages are letters, not direct levers—immutable, copied, queued.

Code as scrolls: single copy, safe hot upgrades.

Why copying beats locking.

Takeaway

Isolation is not a limitation. It is the foundation for predictable performance and fault containment.