A/N: Do you hate programming? Do internships scare you? Do you like the game Detroit: Become Human? If you answered yes to all these questions, then this story might be for you!

This story begins right after the first chapter of the game and will follow Connor as he deals with some, let us say, errors. While there is an OC, there will not be romance between said OC and the game's main characters. I am not against this genre, but it is not my forte, so even if there was romance you most likely would not want to read my novelization of it! That being said, you are the reader and the power of interpretation is in your hands — use at your own discretion! Just know that I intend to keep the relationship between Hank and Connor in the family category; that is, if things go well and they don't end up throwing each other out a window or something.

Updates should be every weekend.

Thank you in advance for taking the time to read :)


Error 202

Chapter One: My Name Is

Written by: Okami of Shinobi Saru Corp


"Hey, Lentz."

Startled, the intern looked up from his monitor, inwardly hoping his boss's next words weren't a reprimand for zoning out. "Yes sir?"

"I am heading out. It's Katy and I's ten year anniversary so I need scoot if I'm going to make it in time for our reservation. You think you can handle locking up for the night?"

Lentz took a moment to let the words sink in. He was stunned. His boss was going to let a mere intern stay, by himself, and lock the place up? Was that legal? And more importantly, did he even know how to lock the place up?

"Lentz?"

It was then the intern realized he had been staring at his boss, mouth agape and eyes glazed over. His body jolted as he regained his senses.

"Yeah, yeah I'll be fine." Anxiety then took over, prompting the intern to ask, "But what about the memory upload for the prototype?" Lentz motioned towards the adjacent room. Through the thick glass, several human-like robots were lined up and attached to different pieces of machinery. The subject of interest was connected via an insert in the back of its neck to a large, central machine, its body motionless as the arms of the machine propped it in place. "The upload is only halfway done. What do you want me to do when it's finished?"

"Ah, right. I almost forgot about that." Dr. Carr, a middle-aged man and one of many CyberLife's directors, directed the intern's attention toward a large, frameless monitor on the far end of the room. On the sleek monitor flashed the progress for the current upload which, according to the loading bar on the screen, was 49% complete. "When that reaches 100 an option to disconnect the android will pop-up. Don't press that."

"Don't press it. Got it."

"Just make sure the basic settings are reset to standard and then run a couple of diagnostics to make sure the upload was successful. After that, shut it down for the night and place the final report on my desk. If the diagnostics fail just make a note and I will deal with it tomorrow."

Lentz quickly processed all the steps in his head. Diagnostics he could do, checking the android's settings sounded easy enough, and he could probably remember how to lock everything up after watching Dr. Lee close the transfer room last week.

"Sounds good. I hope you have a good time at your dinner, sir."

Dr. Carr finished zipping up his jacket and pulled his keys out from his pocket. "Young man, there is one rule for a guaranteed good time when dining with a woman."

The intern cocked his head. "Oh?"

"Pick a place with good food and even better beer." The man winked and then waved goodbye as he walked out the door, his voice trailing as he called out, "Have a good evening. If you have any problems, don't call me!"

Amused, Lentz flashed a small smile. "Goodnight, sir."

The door abruptly slid shut, leaving the intern alone and in near silence. Only the soft murmur of various computers and machines filled the room, their blinking lights adding a hint of red and green to the primarily white backdrop.

Lentz nervously let out a deep breath. His gaze slowly traveled across the room, letting his mind soak in the reality that he, a junior in college, had not only landed an internship during the fall semester at CyberLife, but was also succeeding in gaining the trust and respect of his superiors. And not just any superior, but the notorious Dr. Carr.

He could vividly remember meeting the famed scientist for the first time. The man's cold, grey eyes and strictness had struck fear into his soul during the interview process. But, in a strange way, Dr. Carr's initially fearsome demeanor made any remotely kind thing he said worth more than gold. Lentz had been lucky enough to earn one such word about two weeks prior. Impressive, the scientist had said. Short, to the point, concise — yet that one word possessed more value to Lentz than his long fought for acceptance into Massachusetts Institute of Technology.

A small yet proud smile appeared on the young man's face at the recollection.

Beep.

Lentz looked over at the monitor on the far end of the room. Only 50% of the upload was complete. A long, tired sigh escaped his lips. It looked like he would be staying late tonight.

After readjusting, Lentz settled back down into his swivel chair. Directly in front of him sat his designated monitor along with various, scattered notebooks and pieces of torn out paper. Normally, he would have tried to maintain a clean desk to help give off a good impression to his superiors, but organization had quickly flown out the window after the first week of training. He had heard that those with high intellectual abilities were sometimes the most disorganized people, but he hadn't fully believed it until he had arrived at the Memory Transfer Department (MTD, as most called it) at CyberLife. His desk had started out as a little corner of orderliness but had quickly morphed into the chaos of the rest of the room. Looking up and down the long desk before him, Lentz could no longer tell the difference between his space and the next. It was all just one stream of notebooks, coffee mugs, and diagnostic reports.

Lentz looked out over his monitor and through the panels of glass. The prototype was a dark-haired android who lifelessly stared back at Lentz with a pair of brown eyes. While Lentz loved every second of working at CyberLife, the one thing that never failed to send shivers down his spine was the dead-eyed stare the androids sent his way while their memory was being uploaded. Internally, he knew they were just machines – akin to the computer in front of him but with arms and legs – but they looked so human-like that, when they weren't turned on, they had an uncanny resemblance to that of a corpse. Normally, he would have shrugged it off and tuned into one of the discussions his co-workers were having, but now that he was alone things were a little more surreal.

The sharp ding representing his text tone nearly caused him to jump, out of his seat. Instinctively, Lentz grabbed his phone and read the new message.

Hey bro! I know you are still at work but I managed to find a torrent file online with that old Marvel movie we were wanting to see. I'll email you the link as I accidentally ran over my phone. Texting from mom's phone. Obviously. Duh. Don't ask.

P.S. File isn't bugged… I think.

Lentz shook his head and muttered, "Why am I not surprised?" If it had been anyone else he would have been shocked, but this was his little sister. The same sister who had somehow managed to get her bike stuck in a tree. In the middle of the desert. At midnight.

A notification appeared at the top of his phone, alerting him to a new email. Opening it up, Lentz noted the attached file and skimmed through the short note.

I Googled it. There is only a 40% chance this is bugged. You need to watch this before we go see the new movie this weekend. It is worth the risk.

So watch it or die heathen!

Lentz rolled his eyes. He was on the clock. He couldn't watch a movie on his phone.

The intern glanced around the room until his eyes landed on the main monitor. 51% Complete. Groaning, the young man looked back over at the android. Why was this model taking so damn long to upload? Speaking of, what model was this prototype anyways?

Reading the model number off of the android's jacket, the intern raised an eyebrow. An RK800. He had never seen one of those come through before, though he supposed that made sense seeing as this model was CyberLife's latest and greatest prototype. Or so he had heard. If anything, it definitely looked better than the RK700. One of those had happened to come through during Lentz's first week at CyberLife and the following night he had nightmares about it. Like the RK800, the previous model had dark eyes, but its skin was deathly pale and its hair bleached blonde. It honestly had looked like a disease infested cue tip wearing a jacket and pants.

Out of the corner of his eye Lentz saw the prototype suddenly flinch, causing the intern to sit upright in his chair. Was that... supposed to happen?

Lentz glanced over at the main monitor. Only 52% complete.

Without giving it another thought, Lentz grabbed his phone and started downloading the file his sister had sent him. The memory upload was going to take at least another two hours and he didn't want to be stuck in silence with a twitching android. Plus, his bosses probably wouldn't mind if he watched a movie on his phone when there was nothing else to do. After all, Dr. Carr would often watch old chic flicks on his terminal when things were slow.

The file downloaded quickly, but the intern's face fell as he read the following error message on his phone:

Error: File is not compatible with this device.

"You've got to be kidding me." He could try downloading the movie on his computer, but there was the risk of the file containing a virus to consider. Of course, he could just run a scan to check for viruses, but as an intern working with government property, that would be too risky. And he wouldn't dare put his internship on the line over a-

A loud thud resounded in the adjacent room. Lentz looked up to see that a piece of equipment had fallen over and the RK800 model had turned its head to the side. It was then the intern noticed that the room he was in had dimmed. He glanced back over his shoulder at the windows at the back of the room. The sun had begun to set.

After further consideration, scanning the file seemed like a grand idea to Lentz. He had done this plenty of times with torrent files containing old movies and nothing had happened. Plus, who would try and plant a virus to destroy government level property in a torrent file carrying a movie that came out near 25 years ago? The balance of probability told him he would be fine, and the need to take his mind off of the prototype was beginning to outweigh the need for caution.

Lentz ran a handful of scans on the file. Once he was sure everything looked good, he downloaded the file. Captain America. His family were pretty loyal Marvel fans and, with the new Avengers movie coming out in the next few days, it seemed appropriate to go back and watch more of the original films, even if it meant downloading them illegally off the internet.

Before starting the film, Lentz hovered the cursor over the start button. Did he really want to do this?

His conscious told him no.

Another twitch from the android told him otherwise.

Without giving it another thought, Lentz started the movie. About midway through the film, Lentz felt his eyes start to droop. Curious, he checked the clock on his phone. 9 pm. Some would consider this early, but for someone who consistently wakes up at 4 am, it was near bedtime.

The intern yawned as he reached for the cup of water on his desk. Sluggishly, he brought the cup to his lips and drank slowly…

"Holy shit!" Lentz opened his eyes at the sound of something crackling beneath him. Rolling his chair back, he looked underneath his desk to find his cup of water on the floor. Much to his dismay, the liquid had spilled onto the exposed equipment beneath the desk. Realization crept up on the intern like a snake about to attack its prey.

"Fuck fuck fuck fuck!"

He must have fallen asleep and dropped his cup. Frantically, the intern ran to the bathroom and got a handful of paper towels to clean up the mess. After he had soaked up all the water, he checked his monitor. The movie had returned to the menu screen, the music playing clearly and without distortion.

So far so good.

Exiting out of the movie player, Lentz checked the status of his computer. To his relief, everything looked normal. As one last sanity check, the intern opened up a basic script and ran it on the command prompt. Crossing his fingers, he waited for the output.

Error 202.

The intern's stomach dropped. This was not good. This script was designed to be simple as a way to ensure any issues that arose were not due to an internal problem. The fact that his computer was producing errors after running this was a red flag. More than that, he didn't even know what "Error 202" meant. He had come across indentation errors, syntax errors, and name errors to name a few, but never had he seen this before.

Beep, beep, beep.

On the main monitor was displayed the new status of the memory upload along with a short message:

100% Complete. Would you like to disconnect the subject?

Lentz looked out into the adjacent room. The whirr of the machine had stilled and the RK800 model blinked rapidly as the small, LED ring light on its right temple flashed yellow — all typical behaviors for a rebooting android.

After allowing itself a couple of moments to process, the android said, "Hello. My previous settings indicate that my default language is English. Is that correct?"

Taking a deep breath, Lentz collected himself. Perhaps the script he had run was faulty? Maybe in his panic he had run the wrong one? He checked the script and ran the code once more.

Error 202.

"Well, shit."

Running his hands through his thick, blonde hair, Lentz turned his attention to the newly awakened android. At the very least, he needed to correctly deal with the prototype.

"Don't disconnect the android and make sure the settings reflect the standardized stuff," Lentz recalled aloud. Easy enough, right? Reaching out his hand, he pushed the intercom button near his computer to respond. The intern's voice resounded through the speakers in the adjacent room as he replied to the android's question, "Affirmative."

"Thank you. My previous settings also indicate that my name is Carl, is that correct?"

Lentz bit his lip. Seeing as this was a new prototype he hadn't memorized the standard name for its model line yet. Rolling his chair across the room, the intern grabbed a book out of the plastic bin hanging by the door and swiped through the pages.

"Aha, there you are…" the intern muttered as he scrolled down the page of model names until he found the appropriate one. "RK800, you are called… Connor."

Odd. Why did it think it was Carl?

Book still in hand, the young man looked back out at the prototype who was staring blankly out in front of itself. If the upload had been successful, the android should have naturally resorted back to its standard name. Perhaps the previous version of this model had been given a custom name? After the upload, the new model would have thus resorted to that title, so maybe that was what had happened?

Shrugging his shoulders, Lentz put the book away. Either way, it was best to play it safe and reset the model back to its original settings as instructed. If someone needed to change its name, they could do it on their own time.

Lentz rolled back over to the intercom. "RK800, reset settings to standard."

Promptly, the android replied, "Settings have been reset."

Well, that was fast. "Please state your name."

"My name is Carl."

Lips pursed, Lentz tried another course of action, "RK800, override name."

The prototype's LED flickered. A message on Lentz's monitor popped onto the screen:

Authorization code required for name override.

Quickly Lentz typed in his code. He didn't have access to many things as an intern, but after being with CyberLife for two months, he was granted the authority to perform basic overrides. This marked the first time he had actually gotten to use his newly obtained power; however, the ever tightening knot in chest hindered him from relishing the moment.

After completing the requirements for the override, Lentz pressed the button to the intercom. "RK800, register new name." Lentz paused before continuing, making sure to enunciate the prototype's name slowly and clearly. "Connor."

"My name is Carl."

Lentz's stomach dropped. This was not happening.

"RK800, please override name." Once more the intern typed in his code. "RK800, register new name." This time Lentz raised his voice. Maybe he had spoken too softly before?

"Connor."

"My name is Carl."

Releasing the button to the intercom, Lentz sighed, "No, no it's really not."

The intern leaned back in his swivel chair and ran both his hands through his hair. Closing his eyes, he let out a deep breath. What was causing this to happen? Spilling some water on the computer shouldn't have affected the prototype as the upload was running on the main system. Yes, his personal terminal was connected to that system, but an external issue such as spillage shouldn't have affected anything. After all, aside from the constant error message popping up after running scripts, his computer seemed to be working correctly. Maybe… maybe it was the torrent file?

Opening his eyes, Lentz glanced at his monitor. Surely not. He had run at least three scans on the download before opening it. But… what if?

Jolting up in his chair, the intern reached for the digital keyboard on his desk. There was one thing left to try before giving into the panic within. It was the number one go-to for all computer engineers since the dawn of time: turn everything off and then back on again.

Hurriedly the intern exited out of everything on his monitor, deleted the torrent file just for good measure, and restarted his and the main computer. Before the main system shut down, a message appeared on screen:

Are you sure you want to restart? Restarting this system will shut down all connected networks.

Without much thought, Lentz clicked "yes" and watched as the android in the adjacent room stopped moving. The monitor before him went black and the purr of his computer temporarily ceased. Anxiously, the intern tapped his fingers on his desk as he waited for the system to reboot.

He really hoped this worked. If not… no. He didn't even want to think about what would happen if he screwed everything up. He was just starting to make progress at this place and the thought of losing that made his stomach turn. More than that, what would his father think? Lentz internally winced as visons of his father's demeaning glare flashed through his mind. No, he had to avoid that at all costs. This had to work.

Before long his monitor displayed the CyberLife logo, indicating the system was starting to reboot. In the other room, the prototype's LED started blinking again. Back on his monitor, a prompt for Lentz to enter his password flashed on screen. After typing it in, Lentz sat back and waited, his left fingers crossed for good luck.

Applications started loading onto the screen and a prompt appeared on the main computer that had previously displayed the upload's progress. Rolling over to the monitor to the main system, Lentz read the message:

System was unexpectedly shut down. Would you like to resume from your previous progress?

"Yes please," Lentz said as his finger gently pressed the appropriate option on the touch screen. The next prompt was the same as before, a message asking if he would like to disconnect the prototype.

Raising his brows in cynical amusement, the intern scoffed. Not disconnecting the android seemed to be the only thing he had done right that evening.

Back at his desk, Lentz looked out at the prototype. It had also completed rebooting and was now curiously glancing from one side of the room to the other. Taking a deep breath, Lentz reached for the intercom.

"RK800, state your name."

Focusing its attention on the intern, the android promptly replied, "My name is Carl."

For a moment Lentz was taken aback, not only because the android had once again given an incorrect response, but also because of the slight difference in the way it had enunciated the words. It almost sounded annoyed, like it was tired of being forced to say its name over and over again.

Pressing the intercom, Lentz commanded, "RK800 override name." The intern typed in his code. This was the moment of truth.

"RK800, register new name." Lentz paused as he silently prayed this would work, but before he could utter another word, an error flashed across his monitor accompanied by a loud, high pitched "ding!". Dumbfounded, it took a moment for Lentz to realize what this implied.

"Shit." Lentz suddenly remembered he was still pressing the button to the intercom. He quickly retracted his hand. "Oh fuckin hell!"

Almost immediately, the android responded, "My name is ding!... Shit."

Silence ensued as the intern blankly stared at the prototype. He didn't know whether to be happy that the prototype had actually changed its name, amused at the mishap, or horrified at the new error message flashing on his monitor. The distraught intern let out an agitated sigh as he banged his head upon his desk. He was really grateful no one else was there to witness this disaster; his superiors would have mocked him for weeks.

After taking a moment to collect himself, the intern turned to his computer. First things first, he needed to address this error message.

"A diagnostic report will now run?" Lentz read aloud, pursing his lips as he hovered over the message. "I guess that's okay…" He wasn't sure why this had appeared as an error, but he tentatively allowed the report to run. After all, he needed to run a diagnostic report before locking up, so he might as well let that get started.

Leaning back in his chair, Lentz turned his attention to the erroneously named android. Before reverting the prototype's name back to normal, the intern once again asked the android for his name. Just for good measure, of course.

"RK800, state your name."

"My name is ding!... Shit."

Lentz couldn't help but let out a dry laugh. Not only had the prototype perfectly recreated the message alert, but its calm, methodical voice provided a bizarre contrast to the happy chime of the notification sound. This gave the illusion that the android was displeased, even irked, with its name, something that Lentz found rather amusing.

"Alright, let's get you back to normal." Lentz was about to reach for the intercom when he heard the printer in the back of the room start to rev up. Surely the report wasn't finished already? The intern glanced at his monitor. Contradicting his intuition, displayed on the screen was a message indicating the completion of the diagnostic report.

Getting up from his chair, the intern walked over to the printer. Unlike with everything else, they still used physical paper for their reports. Lentz wasn't sure why this was so, but his current theory was that some higher up had a lifelong hatred of trees. A highly unlikely theory, but not entirely impossible either.

Picking up the sheets of paper, the young man skimmed through the pages. "What the hell?"

Lentz could hardly believe what he was seeing. Instead of a normal report, random strings of numbers and letters were haphazardly scattered across the pages. Everything was spread out in an incoherent fashion, making it look like an extraterrestrial had hijacked their system and spewed out some alien code onto various sheets of paper. The only readable portion was on the last page, printed in bold text:

Ra9 will save them.

"Holy shit…" Lentz didn't know what else to say. His panic slowly started to morph into fear as he continued to stare down at the report, when suddenly the sound of something short circuiting in the other room grabbed his attention.

Looking through the glass wall, Lentz saw the android start to twitch as if possessed by something. The machine it was connected to rattled each time the prototype moved, making Lentz worry that the android might manually disconnect itself. Back in the main room, the computer monitors began to flicker as error message after error message popped up onto the screens, creating a stream of various notification sounds that filled the room.

Before he could even think, a loud noise pulled Lentz's attention back to the android. The prototype was now completely slumped over like a rag doll, still twitching at random intervals. To his left, the main computer system began to whirr, increasing in intensity with each second. As the sound increased, a singular error message began to flash on the monitor, replacing the prompt to disconnect the android with "Error 202". One by one, the message began to appear on each monitor in the room.

The whirr of the main computer reached an ear piercing screech, causing the intern to drop the papers in his hands to cover his ears. Lentz winced and let out a small cry. Pushing his hands closer up against his head, the intern waited until the noise abruptly ceased.

Slowly Lentz removed his hands from his ears and timidly glanced about the room. It was like someone had pushed a reset button. The CyberLife logo was displayed on each of the monitors, save for the main system which once again showed the prompt asking to disconnect the android. In the other room, the prototype had resumed its blank stare. Its LED flashed blue, indicating it was in a stable state.

Behind him, the printer once again started to print, causing Lentz to jump and place his hand over his heart. He was sincerely surprised he hadn't suffered from a heart attack yet.

Cautiously, the intern reached for the pages as they exited the printer. A quick skim of the papers told the young man that it was a diagnostic report for the RK800 model, but this time everything seemed to be normal and readable. Hurriedly, Lentz fumbled through the papers until he found the page with the results of the diagnostic. To his surprise, the results showed that the memory upload had been successful and the android was in top condition.

"There's no fuckin way…" Everything that had happened in the past two minutes told him that this report could not possibly be correct. Unless he had just suffered from a severe hallucination, that is, but the papers scattered about on the ground told him otherwise.

Looking out the adjacent room, the intern locked eyes with the prototype. There was only one way to know for sure.

Slowly, Lentz walked over to the intercom. With great caution, he pressed the button — heaven forbid he mess anything else up — and shakily said, "RK800, state your name."

"My name is Connor."

Without thinking, Lentz squeaked, "A-are you sure?"

Looking slightly confused, the android responded, "Yes, I am sure."

Heart still racing, Lentz nodded slowly. "Huh."

A pause. "Is everything alright? Did I give the incorrect name?"

"Oh, uh," Lentz stuttered as he wiped the sweat that had formed on his face, "No, no. You're good."

Staring back down at the report in his hand, then intern noticed that he was shaking. Deliberately taking in deep breaths, he swiftly stapled the pages together and placed it on Dr. Carr's desk. He would have run another diagnostic as a sanity check — not to mention question what had ordered the second report to print in the first place — but Lentz didn't dare start anything else for fear of causing a repeat of what had just transpired.

As he shut down the main computer, he watched as the android turned off, keeping a close eye out for any odd, twitchy behavior. Nothing. Everything seemed to be operating as if nothing strange had ever occurred.

After turning off his computer, Lentz made his way to the papers he had previously dropped. He swiftly collected them and turned around to take one last look at the transfer room. He really hoped he hadn't skipped anything while locking the place up. Though, to be frank, at this point he didn't care. His desire to get the hell out of there had long since overridden his desire to be thorough.

It was good enough. And with that, the intern exited the room, secured the door, and sprinted for the exit.