INFERNIX ENGINEERING JOURNAL 2026
Notes from the workshop — how the systems on this site were actually built: architecture decisions, measured experiments, trade-offs that didn't fit in a README, and the lessons that survived contact with the benchmarks. Written by Pavan Ganesh Indupudi (Infernix).
Most computer-use agents ship raw screenshots — every email, ID, and password — to a remote vision model. PRIVYSE changes the order of operations: understand and sanitize the page on-device, prove the payload is clean through a fail-closed gate, and only then let the model reason. This is the architecture, the benchmarks, and the two open defects we refuse to hide.
A RAG system that knows when not to answer is worth more than one that always does. How calibrated per-language relevance floors, a grounding guard, and a 56 ms retrieval core came together — and where the borderline zone still hurts.
Running MobileViT inside a browser extension means WebGPU when you can get it, WASM when you can't, and failure modes that only exist at the intersection. An honest draft — the debugging war stories are TODOs until the notes are verified.
Passwords, PANs, and faces deserve different protections. Why PRIVYSE redacts secrets with black boxes, rewrites PII into stable tokens, and blurs pixels — and how Set-of-Marks keeps the model useful after redaction.
