That's Eulix parsing the Linux kernel — and it's what I spend my time building.
I'm Nurysso — systems engineer. I work in Rust and Go, I care about correctness, and I don't ship slow software.
Open-source. Polyglot. Built to understand codebases the way a senior engineer does.
Most RAG systems treat code like documents. Eulix treats it like a program because it is one.
How retrieval works: exact symbol match → keyword → semantic vector → call graph expansion. Each layer only fires if the previous one doesn't resolve — fast path first, expensive path only when needed.
PRISM (Polyglot Resolution via Inverted Symbol Maps) resolves cross-file call graphs in a parallel five-phase pipeline using Rayon. It's the part that makes context actually useful instead of just adjacent.
vanish —> rm that you can undo. Safe, reversible file deletion TUI in Go/Bubbletea.
tyr —> File organiser with local ML inference. Classifies and moves your files without sending anything to a cloud.
Hecate —> Hyprland config that adapts to aesthetic preference at installation.
Rust · Go · TypeScript · Python · Bun · MySQL · MariaDB · Linux
I'm looking for a remote or on-site role in EMEA or APAC — ideally somewhere with a hard problem and engineers who care about the details.
If your codebase is large, messy, or moving fast — that's exactly where I'm useful.
- Email: nurysso [at] proton.me
- Discord: nurysso
