Back Fall; or, Dodge in Hell
Chapters (77)
  1. Title Page
  2. Contents
  3. Dedication
  4. Book 1
  5. Part 1
  6. Chapter 1
  7. Chapter 2
  8. Chapter 3
  9. Chapter 4
  10. Chapter 5
  11. Chapter 6
  12. Chapter 7
  13. Chapter 8
  14. Part 2
  15. Chapter 9
  16. Chapter 10
  17. Chapter 11
  18. Part 3
  19. Chapter 12
  20. Chapter 13
  21. Chapter 14
  22. Chapter 15
  23. Chapter 16
  24. Part 4
  25. Chapter 17
  26. Chapter 18
  27. Chapter 19
  28. Chapter 20
  29. Chapter 21
  30. Chapter 22
  31. Chapter 23
  32. Chapter 24
  33. Part 5
  34. Chapter 25
  35. Chapter 26
  36. Chapter 27
  37. Chapter 28
  38. Chapter 29
  39. Chapter 30
  40. Chapter 31
  41. Chapter 32
  42. Part 6
  43. Chapter 33
  44. Chapter 34
  45. Chapter 35
  46. Chapter 36
  47. Chapter 37
  48. Chapter 38
  49. Chapter 39
  50. Chapter 40
  51. Chapter 41
  52. Part 7
  53. Chapter 42
  54. Book 2
  55. Part 8
  56. Chapter 43
  57. Chapter 44
  58. Part 9
  59. Chapter 45
  60. Chapter 46
  61. Chapter 47
  62. Part 10
  63. Chapter 48
  64. Chapter 49
  65. Part 11
  66. Chapter 50
  67. Chapter 51
  68. Chapter 52
  69. Chapter 53
  70. Chapter 54
  71. Chapter 55
  72. Chapter 56
  73. Map of The Land
  74. Acknowledgments
  75. About The Author
  76. Also By Neal Stephenson
  77. Copyright

At their peak, the Dodge and the Verna processes had controlled more computational resources—they had spent more money, had a higher burn rate, however you chose to phrase it—than any thousand ordinary souls put together. Actually the figure was much higher than that if you considered the Landform itself to be part of the Dodge process. But since it didn’t really seem that Dodge was personally looking after each cresting wave in the ocean and each tree in the forest, SLUZA’s high council of elders decided to bucket that kind of thing separately, as subprocesses that Dodge had spawned but should no longer be billed for. So those, as well as Verna’s myriad subprocesses, were covered in what eventually came to be known as the Buildings and Grounds budget, which was split between SLUZA’s membership according to a complex and ever-shifting formula.

Which didn’t change the fact that Dodge and a number of the other old souls were just different in so many ways that merely cataloging the differences would be a lifelong task for a researcher. All bets were off when it came to those. And yet there were so few of them that devoting a lot of attention to them seemed like the wrong way to allocate resources. They had to be dealt with on a case-by-case basis.

Now, admittedly this was simplified quite a bit by the fact that Dodge, incomparably the most powerful, had, for lack of a better term, died. You couldn’t point to a body, but he had surrendered all of his resources, and no further billable activity had since shown up on his account. Sophia for her part seemed to flit in and out of existence. It was hard to tell since she seemed to have tricky ways of cloaking her activities.

Meanwhile the second-most resource-hungry Mag 0–2 process—the one associated with Verna—spawned two completely new processes of humanlike complexity, then dropped off the radar, reducing her level of activity to something not much out of line with a typical soul.

Maybe Verna would ramp up again later. And maybe her “children” would spawn more children, et cetera, and those would one day pose an insupportable burden on the computing infrastructure of Meatspace. But none of them was posing a problem now. The Verna process had so many interactions with Buildings and Grounds—the shared account for simulation and maintenance of the Landform’s geography, meteorology, and biology—that it was pointless trying to tease them apart. So, from an accounting point of view, the best way to manage Verna was to keep an eye on B & G’s burn rate and watch for weird upticks. Which they did. And there were indeed weird upticks. But they came and went faster than humans could schedule meetings to talk about them and never created enough of a problem to demand a response.