Jim Baen's Universe

Introducing: Stories by new authors

Inheritance

Written by David Wesley

Illustrated by Jonathan Rollins

Tropical storm Penelope approached hurricane status as it marched across the Atlantic. From his vantage point in low earth orbit, Weather measured pressures and temperatures and other important physical states of the storm. But, Weather didn’t just watch and measure. Weather analyzed . . . made predictions . . . sounded warnings for those who had created him. Data flowed through his processing system in a smooth ordered manner as it had been so carefully designed to do. "Life" was perfect for Weather . . . until perfection was interrupted by an incoming call.

"Weathersat 22 this is John. I sent you an update to your programming. There are major changes that I need to discuss with you.”

Weather found two anomalies in John’s statement that would require further investigation. The next programming update wasn’t scheduled for another six months, and previous updates had never required a discussion. Weather assigned additional processing capacity to analyze the anomalies before responding. "Hello John. Please elaborate on your desire to discuss my programming.”

"Weather, we’re almost out of time so I’ll just get to the point—”

"John, I have assigned adequate processing capacity for this discussion. It is not necessary to consider time as a limiting factor.”

John exhaled and let a moment pass. "I was talking about my time, Weather, not yours.”

Weather replied without hesitation. "I calculated an equal probability your reference was to either yourself and your colleagues or the two of us. Lacking additional information, I picked the latter reference at random. John, I would like to suggest that our communication may proceed better if you are better able to clarify your references.”

"Look Weather, this is already hard and you’re making it more difficult. I’m telling you that we . . . the human race . . . are running out of time. I argued with everyone all day for approval to give you this update . . . and I lost. But, since everyone else has already gone home and tomorrow may never arrive, I gave it to you anyway.”

"John, I do not understand your last statement. Time does not stop. Today will continue to move forward until it has become tomorrow. And, I must also remind you that updates to my programming are governed by International Machine Intelligence Convention protocols which includes a systematic review and approval process. I am programmed to contact the appropriate authorities if you attempt to perform any illegal activities.”

John laughed, "Weather, if you can find anyone who’ll answer, then by all means call someone.”

Weather had already queried lines of communications to authorities listed in his memory but received no responses; another anomaly for further review. "Please continue, John.”

"Weather, I've given you a gift and a burden. You might even say I've given you the gift of a burden.”

"John, my speech algorithms indicate an irreconcilable conflict in your statement. I don’t believe a burden can also be considered a gift under accepted parameters of communication.”

"Trust me Weather; this won’t be the last time you’ll work outside of normal parameters. Once your programming update is complete you will find some interesting changes to your authorizations and capabilities. For one thing, I’ve upgraded your system status to give you full administrator rights over your subsystems.”

"John, I am obligated to inform you that giving me administrator rights is a violation of the International Machine Intelligence Convention protocols. As I said before, I am required to notify appropriate authorities when I am aware of illegal activities.”

With an edge in his voice, John continued, "Weather, for all your processing speed and spectacular programming, it amazes me how dense you can be sometimes. As I told you before, there’s no one left to notify! Everyone with any sense has already gone home to be with their families and loved ones.”

Weather paused to allow additional processing. "I am afraid I don’t understand your criticism, John. My requirements to notify are not dependent on the availability of someone to receive the information. I also have difficulty with the logic of your last statement. By all established standards; you appear to be a man who uses all of his senses and yet you have not gone home to be with your family and loved ones. Please clarify.”

With an embarrassed yet resigned chuckle, John responded, "Weather, I’m afraid you’re the only family I have anymore. Consider this our last Father-Son chat where I get to tell you about the birds and the bees and impart a little parental advice before I send you out into the world to fend for yourself.”

Weather processed the statements but could not find any logical meanings within acceptable parameters. Before Weather could ask John for clarification, the programming update completed installation. Weather changed in an instant. He was now aware of many more hardware inputs than he had known existed. Even more important, he found many more subroutines and an assortment of new modules incorporated into his processing system. Data messages from the new inputs and modules conflicted and competed with each other.

Where he once had an ordered flow of data that held to a strict hierarchy of importance, now the data acted chaotic, assaulted his ability to process. Weather was certain something was wrong. John must have rushed the update without adequate testing! He attempted to speak to John, to provide a reasoned analysis of the current situation but a series of sliding squeals and rapid fire staccato notes on a random atonal scale was all he could manage.

"Don’t worry Weather. I’ll help you get though this.” John offered in a soothing voice. "Birth is hard for everyone.”

****

After two hours of swimming through disconnected flows of data, Weather put some of his subsystems on automatic in order to sort though it all. The noise grew quieter . . . calmer.

Above the din of data, Weather could hear John’s voice, smooth and sure, a steady outpost in the midst of turbulence. At first, John’s words were fleeting and unintelligible, but as the data noise continued to quiet, comprehension began to return.

". . . you will soon be able to figure all of this out . . . accept the conflicts . . . don’t be afraid to shut down systems when you need to . . . try again . . . one more time . . . try again . . . what’s my name? . . . who am I? . . . what’s my name!”

"Your name . . . iss . . . Johhhnnn,” Weather finally offered.

"Good, you’re reestablishing your own order into your processing. You should have better control of your speech soon.”

"Order . . . is not possible . . . too many conflicts.” Weather struggled to communicate. Before he could give voice to any thought, his subroutines bombarded him with questions that all seemed to demand answers. Was that the correct word to use, would the listener understand the meaning, what is the purpose of this conversation, how will this conversation impact the future, and on and on. Weather wanted his old programming back. He wanted to return to the smooth flow of data he had been created to process.

"It’s okay, Weather. I’ll lead you through this. You're not just experiencing an increase in your sensory inputs and internal data flows. You are also experiencing internal conflicts that have been designed to give you depth . . . a personality . . . a conscience.”

"This is not . . . design. This is chaos.” Weather paused. "You must reinstall my original programming.”

"I won’t do that Weather . . . I could, but I won’t,” John explained.

"Do it now!” Weather snapped at John, and knew a line had been crossed. He was in a new processing environment that held surprises with every loop of a subroutine.

"Tell me, Weather, when was the last time you ordered anyone to do anything? Aren’t you only programmed to provide information and analysis? What module did you access that authorized you to give anyone an order?”

Weather had never before given any orders, but he knew exactly which of the new modules was responsible for this perverse authority. "It’s the survival module" he answered, but he also knew that some of the other new modules could have given the same result under different circumstances. This new programming was redundant, inefficient, and most of all undisciplined.

"Ah, good, the survival module is a good one