Aevros

The core kernel is operational, including memory management, scheduling, paging, VFS, system calls, and several introspection tools.

I'm currently building the networking stack with the same philosophy as the rest of Aevros: packets shouldn't just move through the system they should be traceable, inspectable, and able to explain where they came from, where they're going, and why.

One design decision in Aevros is that state changes shouldn't happen silently.

When memory is allocated or resources are created, the kernel records ownership and lifetime metadata alongside them. That information powers commands that explain what the system is doing instead of simply dumping internal structures.

The goal isn't to replace traditional debugging tools. It's to make the operating system capable of describing its own behavior from inside the shell.

Most hobby kernels teach operating system concepts well, but when something breaks, you're usually left staring at register dumps or adding temporary print statements everywhere.

I wanted something different.

The idea behind Aevros is simple: if the kernel already knows what it's doing, why shouldn't it be able to explain that?

That idea became the foundation of the project. Instead of relying only on external debugging tools, the kernel records metadata about resources as they're created and uses that information to answer questions about its own state.

It's still a work in progress, but every subsystem is built with the same question in mind:

Can the kernel explain why this exists and what happens if it disappears?