Adult-FanFiction.org : Cartoons

Revelations of Destiny	By : Kellendros Category: Kim Possible > Threesomes/Moresomes Views: 63520 -:- Recommendations : 2 -:- Currently Reading : 2
Disclaimer: I do not own Kim Possible, nor any of the characters from it. I do not make any money from the writing of this story.

Chapter List
- 48
- 49
- 50
Summer Springs Data Store
Thursday, July 7, 10:00

Wade sighed as he finished guiding the Vertibird in for a landing on the open area reserved for him in the Summer Springs parking lot. The computer-assisted piloting controls of the highly advanced, experimental tilt-wing aircraft had responded perfectly, allowing him to set down as if he’d been flying for years, but he wasn’t able to take any pleasure in it. He was too anxious, for a number of reasons.

The biggest thing weighing on his mind was whether or not he was going to be able to find anything in the data store, and if so, would he be able to figure out what it meant—both for Kim and for himself, just to know he could do it. Right up there with it though was his usual nervousness from being out and about in the world instead of home in his room.

Wade didn’t actually have agoraphobia—well, maybe just a touch—but he had become inclined towards a more… sheltered, lifestyle thanks to all the difficulties he’d endured in his twelve short years of life. Over the years, being a gifted and creative super-genius had alienated him considerably from other children his own age, and the fact that he was still a child, with a child’s emotional development—albeit tempered by his considerable intelligence—had usually alienated him from those capable of understanding him on an intellectual level as well. It also didn’t help that he was overweight and he knew it, however much he tried to hide or casually dismiss his self-consciousness over it. The resultant impacts to his warring emotional and intellectual psyche had never been pretty, and it was actually a rather minor miracle that Wade was as well adjusted as he was.

Despite all that, Wade was here now, because he had to be here in person. Sending a remote drone would have most likely been taken as an insult both by the people agreeing to let him into the facility to examine the databanks firsthand, and by the people that had used their influence to convince them to do so—and because he knew that sending a drone to an otherwise safe, secure location any normal person would have come to in the flesh would further marginalize him as a bizarre eccentric amongst his “peers.”

So that was how Wade found himself walking down the ramp at the back of the Vertibird and out onto the smooth black asphalt of the parking lot, while the drone he would have otherwise sent followed along behind him like a faithful dog, trundling along on its polymer plasrubber treads with a soft whirring sound and carrying his equipment in a big, grey, rectangular high-impact polymer toolbox almost as long as he was tall.

Looking around with just a hint of nervousness, Wade adjusted the tie of his otherwise comfortably tailored, casual-cut suit—it had better be comfortable for what he’d paid for it. Spotting the main entrance to the facility—and the small group gathered in front of it—Wade took a deep breath, centered himself, and put on what he liked to think of as his “game face” before releasing the air slowly, striding towards the doors with a confidence he didn’t entirely feel.

“Hello Dr. Thomas, I’m so glad you were able to make it.” Wade was surprised at how warm and soft the bald man’s voice sounded as he stepped forward to greet him—it was totally incongruous with his gaunt, severe features and tall, scarecrow-in-a-suit appearance. “This is my assistant Ms. Lindquist,” the man gestured to the blonde woman on his right, who smiled and nodded shyly, before indicating a mustached man on his left; “and this is our chief hardware engineer Dr. Samuels.”

“Just call me John.” The short man’s informal attitude fit his casual, almost rumpled outfit.

Wade gave a bright smile and a nod to each of them, and then turned his attention to the tall man in the center, shaking his hand as it was offered to him. “Thanks Mr. Whitbee. I really appreciate you allowing me the opportunity to examine your equipment firsthand; I know how unusual that is.”

“Quite all right Dr. Thomas.” Whitbee responded. “It is somewhat irregular, but when I talked to Doctors Sullivan and Xuyin, along with Francis Noble, they all assured me that the interests of the Summer Springs Data Store would be best served by allowing it—and of course, your own considerable reputation helped sway my decision as well. Though I must say I don’t quite know what you expect to find here. All of our recent security checks and regular system diagnostics have shown nothing unusual with our primary systems or the secondary and tertiary backups for them.”

“Well, I’m not entirely sure myself Mr. Whitbee. Right now I’m only following a theory, and I’d rather not say anything else until I’ve had a chance to confirm that theory. But I want to assure you that if I do find anything unusual, you’ll be the first one to know after me.”

“I see. Well then, if you’ll please follow me, I’ll show you around the facility.”

Wade wanted to get started right away, but he knew the pointless ceremony of a tour had to be endured so as not to offend his hosts. Sighing internally, he forced his tone to remain pleasant as he smiled and responded; “Lead on Mr. Whitbee, I’m right behind you.”

The next hour was almost interminable for Wade, but at long last he found himself deep in the heart of the facility, surrounded by the primary mainframes used for data storage and with only John by his side, Mr. Whitbee and his assistant having withdrawn to allow them to work.

“All right John, let’s get to work.” Wade said enthusiastically while commanding his remote drone to set down his toolbox. “First I’ll need a full data-dump of everything in active memory before we start pulling the drives; just give me a minute to get ready here.”

John nodded and started the preliminary setup work while Wade took off his jacket and tie, switching to a special anti-static over-shirt and gloves he retrieved from his toolbox. After that, he put on a tool belt of various slender tools and diagnostic and sensor devices before spending the next five minutes laying out equipment on a nearby table. Once he was done, Wade looked up to find John was ready for the next step.

After dumping all the active memory into a special static data storage module Wade had, the pair went to work painstakingly analyzing the dozen or so hard drives that should have housed the original data Wade had found, using the young genius’ high-tech, cutting edge equipment. Nearly seven hours later, counting the short lunch break they took, Wade sighed and put the housing back onto the last hard drive before handing it to John so he could replace it in the mainframe array.

Wade had scanned every magnetic surface down to nearly the atomic level—and in the process, impressed John considerably with both his knowledge and powerful equipment—but he’d found nothing. Or rather, he’d found nothing he knew should be there. If he hadn’t known firsthand that the data existed and it ought to be there—or at the very least, traces of it if nothing else—he might have begun wondering if he’d imagined it all—or questioning his sanity, as the case may be. As it was, he was merely frustrated beyond any level he’d ever been before.

Looking at his static data module, Wade sighed again. As unlikely as it was, the only thing he had left as a possibility was what was in the active memory. Unfortunately, the odds of anything still being there were next to none.

“Well, I guess that’s that then.” The young genius’ voice was subdued as he turned his gaze to John. “I’m sorry to have kept you here late for nothing John. I can finish my investigation on my own now, so I guess I’ll be going.”

“I’m not sure what you were looking for Dr. Thomas, but a little overtime was worth getting to observe and assist your work. I’ve got to say, you really do deserve your reputation as a leader in the field; I learned a few things today that I didn’t even think were possible.”

Wade smiled modestly. “Thanks John. And please, call me Wade.”

It only took Wade a half-hour to collect everything and leave the Summer Springs facility, waving to John in the parking lot before entering the Vertibird and heading home. Three hours later Wade was walking home from an open field near his house, where he’d landed the Vertibird, his remote drone following along behind him quietly. By the time he reached his front walk, it was late enough that Wade decided to use the side door on the garage so as not to chance waking his parents, who were surely asleep by now.

The only thing Wade took with him when he went inside the house was the static memory module, leaving the rest of his tools with the remote drone until later. As he passed through the kitchen, Wade loaded up on high-energy junk food and pop before heading to his room. As soon as he got inside, Wade piled all his snacks on top of his desk and then hooked up the static memory module to his powerful computer system before getting down to work.

It was many hours later that a dejected, frazzled, bleary-eyed Wade sat slumped forwards at his desk, while the faint grey glow of predawn lightened the edges of his closed window blinds. Not that the young genius took notice. All his attention was fixed on the streams of ones and zeroes scrolling down six of the seven screens spread out in front of him. He’d found nothing in the data yet, but he was sure something was there. He didn’t know how, but something told him it was there, right on the edge of his awareness, just outside his conscious grasp. And so he’d dug and dug and dug until he’d been reduced to examining everything at it’s basic binary level, from the coherent data of the active programs that had been running, to the dregs of fragmented gibberish that had been in the various buffers throughout the system. He knew it was there. Somewhere. He had to find it.

Wade yawned and struggled to keep his focus. There was only so much sugar, youthful enthusiasm, and obsession could do, and the grinding boredom and hypnotically lulling effect of watching base code scroll by was starting to take its toll on the young genius. Blinking, Wade’s eyes lost focus for a second as he yawned again. A moment later, Wade blinked twice more, then his eyes widened in surprise. Jerking upright, Wade snapped fully awake as his hands shot out to his secondary and tertiary keyboards, freezing the data flows on his third and fifth monitors before scrolling back through a few dozen lines on each of them.

“There! That’s it!” The exclamation rang with excitement. In each section of code, thousands of lines apart, were two small scraps barely a line or two long each that seemed to fit together. No normal programmer could have noticed the connection, or even recognized it as relevant instead of coincidence, but Wade’s gifts when it came to coding set him far beyond the level of any normal programmer, and he was sure he was right.

With his hands flying over his keyboards in a whirlwind of typing, Wade quickly cobbled together multiple search algorithms to pick out more likely code fragments within the data streams and set them to searching as soon as each one was finished. After that, he copied the two lines of code he’d already spotted to a separate file, then began his own inspection once more, starting from the very beginning of the collected binary code list, and only using a single screen now that he knew what he was looking for.

Reenergized, the only thing that gave Wade pause over the next several hours was having to go eat breakfast. Aside from that, he immersed himself in the code with a frenetic concentration, going over it line by line until he at last reached the end, and finding another seven scraps of code belonging to the mysterious program along the way. As soon as he was done, Wade checked the results from his search programs, and found they had collected sixty-seven false-positive results and thirteen positive ones, nine of which were the ones he’d already found himself.

Once he finished checking the results and adding the four new code scraps to his collection, Wade took his time refining and retooling his hastily coded search programs before setting the newer, more powerful and precise versions to double-checking the material. While they worked, Wade went over the data-recovery logs to see where each scrap of fragmentary code had been gathered. After a while, he began to get a seed of an idea, but he decided to be patient and wait for his programs to finish running before he acted on it, so instead, Wade tinkered with the code scraps for a while, trying to get a sense of what the program should look like overall, and even managing to put two sections together as a single, longer line.

At long last there was a sharp chirp from his speakers, and Wade looked up at a secondary monitor to find the search was complete. Checking the results, the young genius found that there were only five false-positives this time ‘round, and that the programs had found all the previous code scraps, along with one new one.

Retooling the programs yet again, Wade merged them all into a single combined search engine and took it to cutting-edge levels before setting the thing to triple-check the code list, then he added the new data scrap to the others. After that, he picked up the phone and dialed the Summer Springs facility, asking for Dr. John Samuels as soon as he connected.

“Hello Wade, what can I do for you? Have you found something in the data you gathered yesterday?”

“Well, I believe I might have discovered a few anomalies that support my theory, but I can’t be certain yet.” Despite the fact that Wade was certain he’d found what he was looking for, both logic and caution dictated he hedge with John. Just because his gut told him he was right was no reason to risk his reputation before he could confirm his instincts. “The problem is, I just don’t have enough to go on to be sure yet. However, given the way the information is spread out amongst the data, I think I might be able to correct that, if I can impose on you and the Summer Springs facility for one more day. I need to do full-scale data-dumps on the active memory of all your secondary and tertiary backup systems. From what I saw yesterday, the process should take about four hours. If I left right now, I could be there byyyy…” Wade looked up at the time on his central monitor, “four o’clock your time if I hurry. Would that be all right?”

“I don’t see a problem with it myself, and I’m more than willing to stick around to let you do it, but I’ll have to clear it with Mr. Whitbee first. Can you hold on a minute?”

“Sure thing.” Wade anxiously sat listening to elevator music for the next eight minutes before John finally came back on the line.

“Well, he’s a little annoyed at disrupting our routine schedule for two days in a row, but I managed to talk him into it. I’ll expect you here by four then?”

“Sure thing John, and thanks.”

“No problem.”

As soon as John hung up, Wade was out the door and heading for the kitchen, tossing off a shouted explanation to his mother as he loaded up on junk food and lunch, stuffing everything in a cooler and then rushing out into the garage to collect his remote drone before heading for the Vertibird. Three hours and a considerable amount of highly caffeinated, sugary beverages later, Wade touched down in the Summer Springs parking lot and went inside as quickly as he could. Seven hours after that, he was walking home from the field again, yawning like a demon and barely able to keep upright.

Stumbling into his room in a near incoherent haze, Wade set the three static memory modules containing the rest of the Summer Springs data on his desk, then stood there staring at them for nearly two minutes before he remembered what they were for. Shaking his head, Wade lurched over to his bed and collapsed onto it, fast asleep before he was even able to turn out the lights or pull the covers over himself.

The next morning—or rather, midmorning—Wade was figuratively dragged awake kicking and screaming, and he got up feeling like crap; his eyes crusty and gummy, his mouth seemingly full of used cotton balls, and his whole body grotty from sleeping in clothes he’d worn for well over twenty-four hours straight.

Shuffling over to his computer system, Wade grabbed a half-full can of pop and a handful of Tylenol and caffeine pills from a drawer in his desk, downing them all before fumbling with the static data modules, hooking them up to his system. Once he’d uploaded all the data, he set separate copies of his refined search algorithm to looking through each of the data sets, and then stumbled off to the bathroom to use the toilet before taking a much-needed shower.

An hour-and-a-half later, after one shower and one hearty brunch, a considerably revitalized Wade sat down at his computer system and went to work. First he checked the information gathered from the triple-check of the initial data last night, and found nothing new; the program had found no false-positives and all fourteen code scraps successfully. Satisfied that his refined algorithm was now as tightly-coded as he could get it, Wade checked the ETA on the other three that were running and sighed as he saw there was roughly twenty minutes to go before they finished.

Resolving not to waste the time pointlessly, Wade used the opportunity to filter everything that had come in on Kim’s site as well as update all his legal and illegal news-feeds, checking through everything to find that there had been nothing important happening in the world of crime, natural disasters, or general calamity over the last few days. Just as he was about to move on, his system chirped at him, and Wade quickly shut down the programs he was using and turned his attention back to his real interest.

“Ha! I knew it!” The exclamation came as soon as Wade saw that his search engines had found new code scraps that hadn’t been in the first data-set.

Swiftly cataloging the new information, Wade discovered that there were seven lines that duplicated parts of the data he already had, six more that duplicated parts of the information he’d just retrieved, and thirty-three that were completely unrelated. Copying the fragments to the separate file he was collecting them in, Wade used the new information to further refine his search engine before setting new copies of it to checking each of the data lists again.

Turning his attention to the code scraps he’d recovered, Wade spent the next hour or so pouring over them, managing to rebuild the program into four large chunks and a pair of lone lines that didn’t fit anywhere else. By the time he’d finished the reconstruction work, his search engines had finished their scans, and he checked the data to find two new code scraps waiting for him. After that, Wade made some final tweaks to his search engine and set it to running one last check on the data before he returned to his reconstruction work, finding that the two new scraps went with the two orphaned lines he had.

Now that he had five chunks of program instead of dozens of unconnected lines of code, Wade began trying to work out what the program should look like and how it would function if it were whole. By the time his search engine was done, the only thing that had increased was Wade’s frustration and anxiety. Taking advantage of the respite provided by the distraction, Wade found that no new data had been discovered. Sighing, the young genius reluctantly returned his attention to trying to figure out the program.

Perhaps it was an intuitive leap in logic, or perhaps it was merely the fresh perspective Wade brought with him after the break having supper provided, but hours later, the young genius sat bolt upright and shouted; “Hexadecimal!”

His hands flying over his keyboards typing furiously, Wade restructured the program chunks to reflect base-sixteen coding instead of base-ten. A few minutes later, his grin faded. The adjusted chunks appeared somewhat more orderly and structured now, so Wade knew he was at least partially right, but they still seemed to make no sense. It wouldn’t be until another frustrating hour had passed that Wade got his second spark of insight.

“No… it can’t be…” Wade murmured in disbelief, his brow furrowing with a frown.

Despite his skepticism, Wade transferred the program file off his everyday use system and onto his custom-built, octa-core powerhouse with cutting-edge four-gigahertz processors, sixteen gigs of high speed RAM, and running on a sculpted operating system Wade had personally coded from scratch to be compatible with every major operating system in the world.

Once the file was transferred, Wade ran the fragments through a three-dimensional, fuzzy logic filter, tinkering with various shapes and alignments of the binary code as he did. Three-dimensional layered programming was only at the theoretical stage right now, where code was read not just in one direction, but also aligned to read top-to-bottom and front to back through the layers, and even theoretically through diagonal lines as well. A properly structured three-dimensional code should be able to not only do the work of a program up to a theoretical sixteen times larger than it was, at a rate of up to five times faster, but it also offered a complex branching structure that allowed for easy application of fuzzy logic simulation, granting the otherwise impossible ability for a computer to reach a “maybe” answer instead of the absolutes of “yes” or “no” it normally operated under.

Even though deep down, Wade didn’t really believe he was dealing with a three-dimensional program, he kept running the chunks through various configurations, more to silence his nagging doubts than anything else. Thus it was that when several portions of the chunks suddenly seemed to align coherently, it took the young genius almost completely by surprise.

“No way!” Wade’s mouth gaped in shock.

As soon as he recovered, Wade immediately checked the structure. It wasn’t even close to fully coherent, but several sections of the code seemed to line up on the layers. Shaking his head in disbelief, Wade began running the code through similar structural patterns until, nearly an hour after he’d first started, everything fell into place with a complex fractal star pattern. However, in the instant it fell into place, before Wade even began to register that the program was actually complete, it suddenly vanished off his screen.

Blinking in surprise, Wade checked his filter, thinking it had crashed, only to notice that every file connected to the mystery program had vanished off his entire system!

“What?” The panicked shout of disbelief echoed loudly through Wade’s room as the boy frantically checked everywhere in his system for the files and came up empty. They were gone. The completed program, all copies of the file he’d put the code fragments and completed chunks into, the original Summer Springs data, it was all gone, including his automatic system backups. Somehow they had all been deleted from his system in an instant.

Gripped by a sudden, superstitious panic, Wade immediately ran a check on the four static memory modules he’d stored the Summer Springs active memory data-dumps in, even though he knew that by his own design, it was physically impossible to delete any data from the devices once it was recorded on them—short of opening them up and literally doing it by hand anyway; all the internal recording mechanisms went one-way, with a separate scanner for reading the data once recorded.

Breathing a sigh of relief as he found the data intact, Wade began running through the activity logs of his system, and eventually discovered some minor irregularities that he only noticed because he was sure of what they should have shown instead. The information suggested that something had altered even these files to mask its presence in the system, and more importantly, that that something had also tried to send a power surge through his static memory modules a moment after a failed attempt to alter the data on them was made. That surge had only failed because Wade had built heavy-duty surge protectors into every access point on the devices, even the ones it was largely redundant on, like output ports.

“It had to have been the program.” The low mutter carried certainty and aggravation.

Over the next hour-and-a-half, Wade reloaded the Summer Springs data into his system and ran his search engine to find all the code fragments again, taking hardcopy notes of the locations of every code fragment as he did, just in case. After that, he rebuilt the program chunks and took more notes on how the pieces fit together—again, just in case. After that, he built a separate virtual operating area to manipulate the program in and sealed it off behind a heavy-duty firewall. It would slow the response time down considerably, but that was better than the alternative.

Five minutes later, Wade got to examine the completed program for all of one-point-five seconds as it crystallized into its fractal star pattern before it, and everything connected to it, vanished from his system once more.

Cursing up a blue streak, Wade rebuilt everything as fast as he could, and this time, he isolated the program behind a triple-layered firewall and a double-redundant active permission system that required him to confirm every action his system took, no matter how small. This of course meant that it took him nearly two incredibly tedious hours of clicking “yes” for every little thing in order to run the program through his filter and assemble it again, but it was well worth the reward of finally being able to view the completed program… for all of five seconds.

The only reason a bellow of frustrated aggravation didn’t echo throughout Wade’s house—and possibly the entire neighborhood—was because of how late it was. But it took every ounce of the boy’s self-control to clamp down on that scream and internalize it instead of giving full voice to his ire.

“All right, fine, if that’s the way you want it you frakking piece of crap, then that’s the way you’ll get it.” The low, wrathful growl issued forth from between Wade’s tightly clenched teeth, and moments later he turned intent into action, rebuilding everything in record time before pausing and, instead of starting up his filter, calling up his most powerful three-dimensional graphics rendering program instead.

Working on the art program, Wade quickly rewrote the code so he could “thread” a semi-transparent graphical representation of the program chunks through a fractal star wire-frame. He knew the shape of the fractal star by now, and the radii it used; it might not be as good as actually rebuilding the program, but at least he’d be able to see what it looked like.

It took wade nearly two hours to input the binary code lines into the art program as graphic representations, and nearly as long to manually “hang” them through the wire-frame until he’d managed to align them all properly in a way that seemed to fit together. Two seconds after the last line slid into place, the program shut down and everything vanished. Wade blinked twice in utter shock.

“Oh come on! That’s not even possible!” the sharp exclamation rang loudly through Wade’s room, and an instant later the boy winced and hunched his shoulders, freezing into complete silence and stillness as he listened with anxious concentration, waiting fearfully for the sounds of his parents’ voices. After a few long, tense minutes, he breathed a grateful sigh of relief and turned his attention back to his system.

What just happened was impossible—well, actually, obviously it wasn’t, given it had just happened, but it was the digital equivalent of the Mona Lisa suddenly reaching out of her painting and grabbing a passerby to give them a big kiss. A graphical representation of the program wasn’t the actual program itself. And yet somehow, it had still activated as if it was. Wade shook his head in pure disbelief. What he was dealing with went so far beyond the accepted laws of programming and how computers worked that even he was having considerable difficulty wrapping his mind around even the general concept of how it might theoretically work.

After several long minutes just staring blankly at his screens, Wade shook his head and muttered; “Ok, well, there’s still one thing you can’t escape, and that’s the frakking laws of physics.”

With that, Wade left his room and quietly went down to the basement, where years of old family junk was stored, including several dozen computer systems he’d outgrown in his youth. Armed with only a screwdriver and his determination, Wade proceeded to gut three of the oldest systems in order to build a single system that was just barely capable of running the programs needed to assemble the mystery program. Once he was done, Wade took the open tower case upstairs without bothering to put the panels back on the frame.

Hooking the (relatively) ancient machine up to his system, Wade quickly formatted everything in it and rebuilt the dinosaur with his own custom-coded software before loading it with the programs he would need. After that, on his main system he once again went through all the steps needed to reach the point just before he’d dead-ended so many times earlier tonight, then he transferred the program file over to the dinosaur and disconnected it from all his other systems.

After hooking up the dinosaur to an old monitor from his closet, Wade paused, considering, and then got a high quality video camera from the same closet, setting it up on a tripod and focusing it on the monitor screen so that he would have a visual record of what he was about to do. Once he was sure everything was ready, Wade took a deep breath and released it in a long sigh before stepping back. A moment later he hit enter and waited nearly three minutes for the three-dimensional filter to load into the dinosaur’s running memory.

Wade grinned evilly as he input the parameters and told the program to run. “I’ve got you now you frakker.”

Despite his spiteful enjoyment of the situation, as the minutes dragged on longer and longer with each passing one, Wade began to get restless and anxious. The wait had almost become interminable to him when the program finally fell into place and began its disappearing act. Unfortunately for it, it was now running on a system that barely had enough processing power for it to function on without locking up or crashing, so instead of its previous blink-of-an-eye performance, the complex fractal program moved like molasses, taking over sixty seconds before it finally removed itself from the screen, and nearly thirty seconds more before it managed to delete itself and all traces of it from the ancient system… but Wade barely even noticed. He’d finally gotten a good, clear look at the program in action, its structure and methodology, and he was wide-eyed and slack-jawed from the shock of that revelation.

“No… it can’t be…” the quiet murmur of disbelief faded into the soft background hum of numerous cooling fans as Wade continued to stare at the empty screen with unseeing eyes, his mind a million miles away…
- 48
- 49
- 50
You need to be logged in to leave a review for this story.You need to be logged in to leave a review for this story.
Report Story

Revelations of Destiny