Nanobots, Murder, and Other Family Problems

Chapter Thu 09/22 18:37:11 EAT



The van rattles as we bounce along the dirt track to our camp for the night. Evan lies sacked out in the row ahead of me. I wish I could phase in and out of sleep as easily as he does. Louise, up in the front seat, is chatting with Kofi. Behind me, Jeff stares out the window, a weary look on his lean face. This trip has been good for him. He walks on his own power most of the time now, even when he can find a flat surface to glide across.

We’ve got maybe half an hour before we get back to the others. I like the work here better than the projects in Somalia. Today felt really good. Maybe I’m just used to the heat now, or maybe it’s because it’s not quite so dry here. Or it could be because we actually see the people we’re helping. It’s definitely more interesting than laying pipes through the desert.

Jeff sighs. He looks more than just tired. More like he’s worried. Jeff’s not normally a big talker, but he’s been extra quiet on this trip. I had chalked it up to fatigue, since he’s been working both his muscles and his brains, but he’s stayed quiet even now that it doesn’t look like he’s struggling just to stand up. As he stares out at the brown and green landscape, his gaze is even more distant than normal.

“How are you doing, Jeff?” I ask him. “You holding up OK?”

“I am fine.”

“You’ve just been quiet lately.”

“I suppose I have,” he answers, turning to look at me. Weird, he almost never looks at you with his regular eyes.

“Something bothering you?” I probe.

“Actually, yes. There is a problem that I am having trouble solving.”

“Cooking up some new code? I’m surprised you have the energy. I’ve been too wiped out all trip to even think of working on any of my projects.”

Jeff pauses a moment. My overlay shows a bot eye forming from Jeff’s cloud and zipping past me to take a look at Evan’s sleeping form.

“No, it is not anything like that,” Jeff answers after a moment, his bot eye dissolving. “It is about Father and his dump truck full of nanobots. It should not be possible. At least not with any abstraction that I have been able to figure out. You can coordinate groups of nanobots. The software built into the phone’s controller does that easily. You can even coordinate groups of groups, as I demonstrated in the code I shared with you. That is how I enable my larger cloud.” He shakes his head slowly, his mouth pulling into a frown. “But if you were to try to take that abstraction to a higher level, you would need some adaptive and dynamic automation to optimize the management of the lower level functions. Lacking that, your efficiency would drastically diminish. But Father’s efficiency does not decrease when he coordinates the efforts of a larger cloud. If anything, he appears to be more efficient the more bots he is running.”

It takes me a second to parse all of that. I have to read back through it twice in my log before I’m sure I understand what he’s getting at. “Wait, you’re saying he gets more effective per bot when he’s handling more of them? That doesn’t make sense. Are you sure?”

For a long moment I just hear the hum and bumps of the road beneath us.

“Yes. I have been observing quite closely,” he says finally, staring out the window again. “He has been leaving a large number of nanobots behind for maintenance at each of our build sites, so his cloud size has been fluctuating significantly. The math is complex, because I have to figure in the decreased total productivity from having fewer bots and then figure out the delta in his efficiency. My expectation would be that when he finishes a job and loses some bots to maintain it, he should get more efficient on a per bot basis because his control can be more precise, but less productive overall, because he has fewer nanobots to work with. So I have plotted what I expect the net effect would be whenever he disconnects bots from his cloud. But the observed reality doesn’t match that. He seems to be getting less efficient as he loses nanobots, so the total productivity drop is much larger than I would have expected.”

“So?” I ask. “Maybe he’s just excited in the mornings when he starts and gets tired through the day.”

“A valid point, which is why I also factored that into my calculations. But there is more to consider. When I was running the pipes in the large plant, he was building around them. He did not know where I would place the pipes, so there was no way for him to have programmed the changes to the design in advance. The blueprints were adapting. The design was changing, even where he was not looking. His cloud was making decisions on its own.”

That could only mean one thing. Unthinkable. Not even Father would do that. “Wait, you don’t—”

“He is running adaptive controls on the nanobot cloud’s internal processors,” Jeff interrupts. “The processors in each individual nanobot are using learning intelligence. That is the only explanation that makes sense. When he loses nanobots, he loses both workers and computational resources.”

Warring sensations of elation and terror course through me. If he’s right—and I can’t imagine he’d say this if he weren’t sure—then Father is more dangerous than I had thought. If he’s offloading controls to his cloud’s processors, his cloud could have all sorts of contingencies and reactions built into it. They could do work independent of his control. He could have any number of programs that get triggered if he’s incapacitated or killed. Maybe it’s a good thing I didn’t crush his head with a rock back in Djibouti.

On the other hand, I might have an ally here. Jeff seems even more disturbed about it than I am. This goes against every rule about safely using nanobots. If he’s running adaptive AI on the bots, he’s only a small step away from a potential Gray Goo event. One bug in the software is all it could take to have uncontrolled reproduction consume everything on the planet.

Does Jeff understand the full implications? And if so, what is he willing to do about it?

“But that’s illegal,” I say, probing him. “That’s against laws that he helped to write. You don’t think he’d do that, do you?”

He turns and gives me a long look.

“Noah, you have only known Father for a few months,” he says softly. “But based on your experience with him, do you think that he is the sort of man who would let rules of any sort prevent him from doing what he thinks needs to be done?”

“No, I guess not.”

“Indeed,” he says, his voice turning firm. “If he thinks that breaking rules is necessary, he will do it without hesitation. Even if the rules were his own creations.”

“Isn’t that dangerous though?” I say, feigning ignorance to see his reaction.

“In this case, Noah, it is the most dangerous thing in the world.”

Perfect. “So what do we do?”

“I am not certain.” Jeff turns back to the window. “I need more time to consider. I am very concerned. Please keep this between us. I do not want to worry the others. They do not all have the temperament necessary to handle this information discreetly.”

“Of course,” I reassure him.

With any luck, he’ll come to the same conclusion that Louise, Andrea, and I came to last night: that Father’s behavior can’t stand, and we’re the only ones that can do anything about it. From there, it’s not a big jump to needing to kill him. For Jeff, he needs to think that it was his idea. That’s the only way he’ll go for it. If he realizes I’m pushing him that way, it’ll backfire. That’s OK. I’ve waited this long, I can wait a little longer to get another sibling on my side.

Jeff settles back into the seat and closes his eyes, deep in thought. I do my own thinking, pondering all the ways I could use him to my advantage.


Tip: You can use left, right, A and D keyboard keys to browse between chapters.