Scene 00 — Open
Self-taught builder working out of Kathmandu Valley, Nepal. AI assistants, developer platforms, camera apps — shipped solo, documented like someone else has to pick it up. Because eventually, someone will.
Scene 01 — Origin
Most AI assistants assume a GPU. Mine doesn't. Every wake-word detector, speech model, and pipeline has to earn its place on a 13th-gen mobile CPU with 16 GB of RAM—no cloud, no shortcuts. That constraint is the point.
I build the way I'd want to inherit a codebase: documented, dependency-aware, and honest about what's broken. Sometimes the next reader isn't even human—it might be an AI agent continuing where I left off.
Four projects, four names that sound bigger than the code behind them. A vault, a sentinel, a protocol, a mesh. I'd rather ship something small that works and be honest about it than let the name do the talking.
System Spec — Main Rig
Scene 02 — The Builds
CIPHERWRAITH — Quantum-Grade Credential Vault
A zero-trust, encryption-at-rest credential vault engineered for a post-quantum threat landscape — every secret sealed behind symmetric authenticated encryption before it ever touches disk.
The "quantum-grade" part is a `cryptography.fernet` call and a JSON file. It's a password manager. It works, it's genuinely fine, and I will not be elaborating further.
SENTINEL-X — Autonomous Intrusion Deterrence Matrix
A continuous network-perimeter monitoring system with anomaly-triggered alerting — watching uptime at the edge so downtime never goes unnoticed.
Pings my router every 5 seconds and writes a line to a .txt file when it doesn't answer. "Anomaly-triggered alerting" is a print statement. Ten minutes, start to finish.
GHOSTPROTOCOL — Zero-Trust Biometric Access Framework
A vision-driven, identity-gated access layer — nothing unlocks until the system recognizes who's asking.
It's face detection from an OpenCV tutorial, wired to unlock one folder. "Zero-trust biometric framework" is doing a lot of heavy lifting in that sentence.
VOIDLINK — Ephemeral Distributed Messaging Mesh
A self-destructing, node-to-node communication layer built for messages that shouldn't outlive the moment they were sent in.
Two Flask servers on localhost pass messages that delete themselves after 10 seconds via `setTimeout`. "Distributed mesh" is one server talking to one other server.
Scene 03 — On the Bench
Web
HTML5, CSS3, JavaScript
Backend
Node.js, Python
Systems
C, C++
Cybersecurity
OSINT, password cracking, security fundamentals
Editors
VS Code, Cursor
Tools
Git, GitHub, Linux
Final Scene — Get in Touch