Returning to Dominate The World With My Knowledge System
Chapter 67: Building the Operating System

Chapter 67: Chapter 67: Building the Operating System

Tyler woke up to a soft flicker of sunlight pressing through the hotel curtains.

It was already afternoon.

The quietness of the room and the cool air, coupled with how light his body felt made him feel like he was floating.

The ache in his arms, the tightness in his back, and even the burn behind his eyes was gone.

Though not completely, but enough to let him know that his crash into sleep the night before had done what it was supposed to do.

He sat on the edge of the bed for a moment, letting his mind adjust. His body felt light but his mind hadn’t fully caught up.

With a deep breath, he stood and moved into his routine. He brushed and took a long shower, then changed into a clean aef5of clothes.

By the time he was slipping into his shirt, he kind of felt like a different man.

It was the kind of feeling you get when you wake up on the right side of the bed and if things are working out just fine for you.

After he was for putting on his clothes, Tyler stepped out of his room and headed toward the elevator.

On the way down and as he rounded the hallway corner, he bumped into David.

David’s face lit up with relief the second he saw him.

"Finally," David said, giving him a mock scolding. "I was beginning to think you died in your room."

Tyler offered a light smile, as he greeted him.

David laughed and fell into step beside him. "I assumed you’d wake up half-starved. Come on, let’s get you something to eat."

Their conversation stayed light as they descended toward the hotel cafeteria. Their conservatory was nothing important, just easy words.

Light mention about the weather, the happening with Gumua’s government and how much they now depend on VaultPay for their every transaction.

Tyler responded, taking note of everything David was saying but his mind was already elsewhere.

His mind was on the operating system.

The moment he entered the cafeteria, the smell of grilled meat, fresh bread, and lots of delicacies hit him hard.

It had been a week since he came to Gumua and the truth was that he was already craving his mother’s cooking.

And the most saddening thing was that he has no idea when he will have the chance to return home.

Tyler sighed heavily and turned his attention to what he would order. Though he was craving his mom’s cooking, he didn’t hesitate to place his order as he loaded up a plate like a man who had fought a war.

He sat down and immediately started eating fast, wolfing down his food.

David who say across from him, didn’t say much as he just watched him eat.

As he ate, Tyler’s thoughts drifted to the most important thing at the moment, the operating system.

Heimdall, the custom computer had been built. Though he hadn’t tested it yet but Tyler was sure that it would work just fine.

And to work, what it needed was an operating system.

And not just any operating system but an AI-first OS.

Under normal circumstances, creating an operating system from scratch wasn’t something people just did.

It took thousands of engineers, years of refinement, testing, rewriting, compiling, error-tracing.

Operating systems weren’t just software. They were ecosystems. A delicate dance between hardware management, user interaction, resource scheduling, and stability maintenance.

And there are things he needs to consider before even writing a line of code for the operating.

Memory management: How would the OS handle volatile and non-volatile memory? Especially on a device with 64TB of RAM and 192TB of advanced storage.

Process scheduling: What logic determined which operation got priority when the system was juggling millions of concurrent instructions?

Interrupt handling: What happened when one of the RISC controllers fired an alert, or when the AI needed emergency allocation during a training loop?

File system architecture: Would the OS use a traditional hierarchical model? Or would it require a neural, graph-based index for AI workflows?

Security layer: With so much raw power, Tyler couldn’t risk even the smallest vulnerability. Every controller, every data call, every thermal spike had to be monitored, filtered, authenticated.

The list went on and on.

In a normal case, he’d have needed a whole operating system division, with teams specializing in nothing but device drivers, UI rendering, runtime libraries and IO schedulers.

But Tyler’s case wasn’t normal because what he was building wasn’t a regular operating system.

Tyler wasn’t trying to support a million users. He didn’t care about driver support, commercial compatibility, or pretty interfaces.

He was building an OS that would only ever exist on one machine, which is Heimdall.

And Heimdall wasn’t built for spreadsheets, browsers, or gaming. It was built for a new kind of intelligence.

So the OS had to be more than just software. It had to be AI-native.

Not just AI-friendly, but built from the ground up to serve, support, and enhance AI processes.

That changed everything. It meant the OS itself had to learn and it had to evolve.

Thankfully, Tyler had [Computational Mathematics].

His knowledge wasn’t just theoretical. It would allow him to create autonomous logic agents—self-contained bots that could manage subsystems, test edge conditions, and simulate behavior trees in real time.

He could use it to develop semi-AIs—not full consciousness, but enough to handle various pieces of the OS build intelligently.

Even so, it would still be difficult. Extremely difficult.

There was no world where he could create the entire OS in one stretch, alone and without error.

That’s why he had a plan.

He’d build the OS to a stable baseline. He will build it just enough for Heimdall to boot, for the Valkyrie-X chips to coordinate, for memory, cooling, and storage protocols to respond as expected.

Then, he would stop, because that’s where the real leap would begin.

Tyler wouldn’t finish the OS manually. Rather, he’d embed the logic of the OS into the AI he planned to build next.

That AI would then finish the OS. It would rewrite parts of it, restructure it, tailor it and optimize it for itself.

Yes, jt sounded impossible and sounded like something from a movie.

But Tyler had been doing the impossible since the day he got his second chance at life.

This would just be one more line in a long list of ridiculous wins for him.

He finished his meal and pushed the plate away. David had already left halfway through, letting him eat and think in peace.

Tyler stood up, feeling full but not sluggish.

He stepped into the elevator and rode it up to his room. Once inside, he crossed the room, and sat on the bed.

He picked up his laptop from the nightstand, opened it and launched his IDE.

He stared at the blank project file for the operating system for a while, as it’s on it that he would start developing one of the things that would define the future.

Then he typed the name at the top of the screen: Aegir.

Tyler cracked his knuckles, leaned forward, and began writing the first lines of code.