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?