I’ve always been obsessed with what happens beneath the surface of software.
In a world where modern tech often feels like layers of wrappers running on top of rented cloud servers, I wanted to understand—and build—the foundational pieces from scratch. That curiosity led to creating the AROM Sovereign Matrix, an ongoing endeavor to rethink computing from bare-metal kernels up to autonomous, deterministic intelligence.
Most of my days are spent grappling with hard low-level engineering problems:
Writing and debugging microkernel schedulers, virtual memory managers, and ring-0/ring-3 isolation in C++ and Rust.
Figuring out how to give language models genuine cognitive continuity through external state layers like Enx, rather than just shoving context into ephemeral vector databases.
Exploring neuro-symbolic runtimes and liquid cognition that prioritize deterministic logic over probabilistic guessing.
Building tools, compilers, and privacy-first OS forks designed to return ownership and autonomy back to engineers and users.
I don’t believe in treating technology as magic or accepting vendor lock-in as inevitable. Building deep infrastructure as an independent developer is messy, humbling, and full of edge-case bugs that break in the middle of the night—but it is also deeply rewarding.
I started this blog on Hashnode to document the reality of that journey: the architecture decisions, the failed prototypes, the kernel panics, and the breakthroughs. Whether you’re deep into systems programming, fascinated by AI memory architectures, or simply believe in a more sovereign digital future, I hope you find something here that challenges your perspective or helps you build something resilient.
When I’m not compiling code or inspecting memory dumps, I’m usually reading research papers, testing new language grammars, or refining the next layer of the AROM stack.