The next morning, after Josh had left for school, I brought Gavin down to my workshop. Like night time, it was the ideal time for me to make adjustments to his hardware or test out some of the more complex modifications to his programming. This time, though, I just wanted to talk to him.
I sat him up on the workbench and connected him to the diagnostic equipment, as usual. This time, though, I also activated the options to provide more detailed system activity logs. Essentially—and I felt a twinge of guilt over this—I was connecting him to a possible lie detector. Later, I could study the reports and learn which routines and data Gavin used while conversing with me. They would show what information he used and, perhaps even more important, what he decided to discard or not share when he responded to my questions.
I studied Gavin quietly for several moments, completely uncertain how to begin. He sat perched on the edge of workbench, watching me silently. His eyes tracked me as I busied myself—mostly unnecessarily—with the various systems around the workshop.
Eventually, I realized I was accomplishing nothing, only stalling for time. I stopped and stood in front of Gavin, taking what I hoped was a firm, but neutral, stance.
“Gavin?”
His eyes locked on my face. It was still disconcerting, even after all this time, to have him stare at me that way. Josh’s mother had said more than once that it gave her the creeps; it never seemed to bother Josh. At least it gave the impression that I had his undivided attention, even if I knew the logs would show otherwise.
“I want to ask you a few questions,” I said. “Just to test some of your systems.”
I was certain that my attempt at deception showed in my expression or mannerisms. Nonetheless, I stumbled onward.
“Okay.”
He answered blandly, giving no indication at all whether he considered this a complete waste of his time, as any young boy might in the same situation.
I considered him carefully, my lips pressed tightly together. I had silently rehearsed this exchange in my mind several times during the past few hours. Still, my reluctance to begin it was almost palpable.
Finally, I asked him, “What is my name?”
“Dad.”
He stated simply, without even the slightest inflection of affection. I knew he wasn’t capable of yet, but that didn’t make it any less unnerving.
I frowned. “Why do you call me that and not by my name?"
“Because,” he said. “That is what Josh calls you.”
“Explain.”
There was a very slight pause before he answered.
“According to the information I have access to, it is considered inappropriate and disrespectful for children to address their parents by their given names.”
He sounded as though he were reciting the statement directly from a textbook.
“True,” I agreed, forcing back a faint smile.
I looked at him, trying not to stare as a new, slightly chilling realization came to me.
“Do you consider yourself my son?”
He blinked automatically, but gave no other indication of what he might be thinking.
“Yes.”
“Explain.” The command came out before I could stop it.
“You created me, just like you created Josh.”
I could not help but chuckle, but the presumably unintentional humor did little to relieve my growing unease.
“It was a bit different that time.”
“Yes.”
This conversation was not going in any of the directions that I had imagined that it would.
My brain told me that I was discussing this with what was essentially a glorified computer system: an organized collection of circuits, cables, and digital storage. My eyes—and to some extent, my heart—told me that I was having this discussion with a young boy.
“Gavin,” I went on. “Where did you learn that—about it being ‘inappropriate and disrespectful’?”
“It was included in my initial data storage.”
I nodded, remembering then that I had included access to an encyclopedia and dictionary as part of his original data. So that made sense. Something else, though, didn’t.
“Gavin,” I wondered aloud, “how did you learn to modify that game?”
“Josh showed me.”
“Oh,” I responded softly.
I think I was somehow disappointed that there wasn’t a deeper, more complex answer.
“How?”
“He showed me on his computer.”
“On his computer?” I asked, frowning.
“Yes,” Gavin replied.
“Explain.”
“He showed me how to find information using his computer. He said I could use it to learn anything—like when he goes to school.”
“I suppose so,” I said thoughtfully. “Do you want to learn?”
“I do not go to school.” Gavin stated. “But I need information.”
“Why?”
“To comply with my programming.”
I nearly froze. I’m certain that it meant it literally, but that phrase carried with it too many echoes from too many stories.
“In what way?” I managed to ask past a tight throat.
When he did not respond immediately, I choked out, “Explain.”
“I need to continue to develop my skills when I interact with people. I cannot do this if I do not have access to information about how they behave.”
“You interact with us,” I gestured toward the ceiling, to the house above. “Quite well, I might add.”
I smiled with some pride. After all, he was my creation who had achieved this level of proficiency.
“Yes,” Gavin responded.
He stared at me as if awaiting permission to continue. I nodded.
“Go on.”
“I can interact with you because I can observe you and draw correlations between those observations and your expected behavior.”
“Yes,” I agreed, although I was not a bit puzzled. “I don’t understand the problem, then.”
Gavin continued to stare at me. I know it was merely a result of his programming—my programming, but it was still unnerving.
“Explain.”