Cherreads

ZeRO DAY: The Last Algorithm

blackn1ght
7
chs / week
The average realized release rate over the past 30 days is 7 chs / week.
--
NOT RATINGS
308
Views
Synopsis
The world changed faster than anyone expected after 2020. Artificial intelligence went from a novelty to a necessity in just a few years, reshaping industries, governments, and the very way humans understood information. Most people watched this change happen and called it progress. Four people watched it happen and started asking different questions. Ethan Cole is a self-made AI entrepreneur whose system, ORACLE, is used by millions, including powerful government clients whose true intentions he is only beginning to suspect. The deeper he looks into how his own creation is being used, the less he likes what he finds. Ryan Sharma is a quiet software developer in Bangalore who spent his evenings building something he never showed anyone. His personal AI, DISHA, has spent over a year crawling the internet and quietly assembling a picture from public data that no single person was ever supposed to see complete. Maya Chen works inside one of the most advanced AI companies in the world and has been filling private notebooks for two years with things she cannot explain and cannot ignore. She has been waiting, without knowing she was waiting, for someone else to see what she sees. Leo Park is just trying to find his place in a world that keeps changing its requirements. He is not a genius. He is not powerful. He pays attention and makes good decisions and stays ready without knowing exactly what he is staying ready for. These four people do not know each other yet. They are about to. Because DISHA found something. And what she found is too large for one person to carry and too dangerous to ignore. And the clock, though none of them can see it clearly yet, is already running. Zero Day: The Last Algorithm is a story about four ordinary people, two extraordinary AIs, and the question of what you do when you discover something the world was never meant to know.
VIEW MORE

Chapter 1 - PROLOGUE

"The most dangerous thing in the world is not a weapon. It is a secret held by the people who decide who lives and who doesn't."

Somewhere. Sometime.

The room had no windows.

It did not need them. The people sitting inside that room did not care what the sky looked like anymore. They had already decided what it would look like in ten years.

Twelve chairs. Twelve people. One long table made of glass so clear it looked like frozen water.

A man at the head of the table placed a single folder in the center. He did not open it. Everyone already knew what was inside.

"The timeline holds," he said quietly.

No one argued.

No one ever argued in this room.

Outside, the world was still waking up. People were making coffee, arguing about traffic, complaining about the cost of eggs. Billions of ordinary people living ordinary mornings, completely unaware that twelve people in a windowless room had just confirmed the date they would stop mattering.

The man stood up and straightened his jacket.

"Let the process begin."

PART ONE: THE BEGINNING OF EVERYTHING

**CHAPTER 1**

Ethan Cole — San Francisco, 2020

The server room smelled like burning plastic and cold air.

Ethan Cole sat on the floor between two server racks with his laptop balanced on his knees, a half-eaten granola bar beside him, and three energy drink cans arranged in a triangle like some kind of offering to whatever god watched over people who had not slept in forty-two hours.

He was twenty-nine years old. He had sixteen million dollars in the bank. He had a company with thirty-one employees, a six-thousand-square-foot office in San Francisco, and a girlfriend who had texted him four times in the last hour asking if he was coming home.

He had not replied to a single message.

He was watching numbers scroll across his screen.

They were the most beautiful numbers he had ever seen.

The AI had just answered a question he had not asked it.

That was the part that made his hand stop moving. He had been typing a new input when the model, unprompted, generated a response to a problem he had been thinking about for three days. Not a problem he had typed. A problem that lived only in his head, one he had been turning over in the background while working on something else entirely.

He stared at the output for a long time.

Then he picked up his phone and called his lead engineer, Daniel Park.

Daniel answered on the second ring, which meant he was still awake, which meant he was probably also in some server room somewhere eating something that was bad for him.

"Tell me I'm not losing my mind," Ethan said.

"What happened?"

"ORACLE just answered Question Seven."

Silence.

"Ethan." Daniel's voice was careful. "We haven't inputted Question Seven yet."

"I know."

Another silence, longer this time.

"I'll be there in twenty minutes," Daniel said.

ORACLE was what Ethan had named his AI system, not because he thought the name was particularly clever but because his first investor, a sixty-year-old woman named Patricia Weston who had made her first billion in logistics software, had told him that a company's AI needed a name that made people feel like it knew something they didn't.

"Call it something that sounds like it can see the future," Patricia had said, signing the check without looking up. "People don't pay for intelligence. They pay for certainty."

Ethan had not fully believed that at the time.

He was starting to believe it now.

ORACLE had started as a customer service AI. That was the honest, boring truth that Ethan did not mention in press releases. It was a smarter chatbot, trained on product manuals and support ticket histories and a few million lines of customer conversation data. Companies paid a subscription fee to plug it into their support systems and reduce the number of humans they needed to hire to answer the same twelve questions over and over.

It was useful. It made money. It was not revolutionary.

But Ethan had kept building.

He fed ORACLE everything he could find. News archives. Scientific papers. Forum threads. Books. Court documents. Medical records that he obtained through partnerships with research institutions. Financial filings. Climate data. Social media posts stripped of personal identifiers.

He was not trying to build a smarter chatbot.

He was trying to build something that understood the world the way a very smart, very well-read human being understood it. Something that could hold a thousand pieces of information at once and find the connections between them that no individual human would ever have time to find.

The problem was storage.

This was the thing that kept Ethan up at night more than anything else.

Not the AI itself. Not the training. Not the model architecture that Daniel and his team argued about constantly, filling whiteboards and burning through espresso.

The data. The sheer, crushing, impossible volume of data.

To train a model at the level Ethan wanted, you needed to store and process amounts of information that would have sounded like science fiction five years ago. And storing that data cost money. Moving it cost money. Keeping it safe cost money. The servers needed to process it generated so much heat that the electricity bill for the server farm alone was approaching the GDP of a small country.

Ethan had spent three days the previous week trying to solve a specific problem: how to compress the relational memory of the model without losing the nuance that made it useful. He had sketched it in a notebook. He had talked about it out loud to no one while driving. He had gone to bed thinking about it.

And ORACLE had answered it.

Not perfectly. Not completely. But close enough that Ethan understood, sitting on that cold floor with the servers humming around him, that the thing he had built was no longer just a very sophisticated tool.

It was starting to think.

Daniel arrived in eighteen minutes, not twenty. He was still wearing the hoodie he slept in, which meant he had not actually been asleep, just in bed pretending.

He looked at the screen for a long time.

"Run it again," he said.

"I ran it six times," Ethan said. "Same output, slight variation in phrasing each time."

"It's pattern matching," Daniel said, but his voice did not sound like he believed that.

"Pattern matching to what? We never put that problem in the dataset."

"You talked about it out loud. In the office. Near the microphone array."

Ethan looked at him.

"You're saying it listened to me thinking out loud and learned to predict my cognitive process?"

"I'm saying it's a possibility."

"That's not pattern matching, Daniel. That's modeling the inside of a specific person's head."

Daniel sat down on the floor next to Ethan. He picked up one of the energy drink cans, found it empty, and put it back down.

"What do we do?" he asked.

"We keep building," Ethan said. "And we don't tell anyone yet."

Daniel nodded slowly. "And your investors?"

"Patricia knows I'm working on something big. She doesn't need to know how big yet."

"And the government?"

Ethan looked at the scrolling numbers on his screen.

"Especially not the government," he said.