sacrvm — Latin: “a sacred thing; a rite.” Also MARCVS, rearranged.
Full-stack developer, architect, tech lead by day — .NET, Azure, and whatever else the project needs. Visionary by night, using AI to raise thirty years of craft to a higher power. What lives here are the private passions.
A suite of DJ tools on one shared engine: analysis, tagging, playback and broadcast, installed side by side on a single runtime. Key, BPM, energy and loudness detection built for harmonic mixing — not a plug-in for someone else's library, but the library itself.
A UI kit for the web with no build step: forty-one sac-* web components, every colour derived from one --accent variable, and an app system that installs apps by URL. Vendor one folder of plain files, write HTML — no framework, no bundler, F5 is the toolchain. The proof runs at desktop.sacrvm.dev: a desktop in your browser, its apps served from anyone's repository.
The Pascal CRT unit, reborn for modern .NET CLIs: TextColor, GotoXY and friends, truecolor with graceful fallback down to NO_COLOR, nine built-in themes, and curated blocks from framed banners to spinners. Tiny, dependency-free, AOT-clean — with Snake, Tetris and Invaders in the repo to prove it.
The launcher your .NET app doesn't have to write: Husky starts it, watches it, restarts it when it crashes, and fetches updates from GitHub Releases or a plain JSON manifest — graceful stop, binary swap, back up again. Three lines of Husky.Client and any long-running app ships with supervision and self-updates built in. Woof.
A native Windows shell that hosts AI agent sessions — Claude Code and friends — in tabs that glow from igniting to embers. WPF and ConPTY, no Electron in sight; an MCP bridge lets the agents inside open tabs, message neighboring projects, and search a shared knowledge store. Local-first, self-updating — and the page you are reading was written in it.
Every number in my code is one of three things: measured, derived, or chosen — there is no fourth case. Claims keep the measurement that produced them, and when one turns out wrong, the retraction stays in the file.
The expensive bug is not a wrong calculation — it is a correct calculation on a false premise, because nothing breaks. A surprising result gets checked against something external before it gets believed.
There is no undo, by design. Anything that moves, renames or deletes your files says exactly what it is about to do, names every file it will touch, and waits.
Each project keeps a ledger of what is known to be broken and what was built on top of it anyway. A workaround that lives only in code gets explained away — and an empty list proves nothing.
Verdicts come from the product — the built executable, the real screen — never from a flattering preview. A green test that proves nothing is a bug like any other.
Agents build for me around the clock, budgeted and scoped. Nothing they make is committed, shipped or believed until my own eyes and ears have signed it.