I build the parts of a system that must not fail — money paths, concurrency controls, telemetry pipelines, and cryptographic migration protocols. I don't do vibes-based engineering: every claim below is backed by a repository, a CI run, or a test that re-proves the behavior on every push.
Press the buttons. Audit the evidence. That's the whole pitch.
V-01 · VoltHub-CSMS — Two-engine EV charging management where the money path and the telemetry path are deliberately different databases: Oracle 23ai owns ACID billing + reservations, TimescaleDB owns high-volume telemetry. An OCPP 1.6J gateway drives a simulator fleet, and CI race-tests both engines on every push. Ships with a typography-led Next.js operations console, Codecov coverage, release automation and an OpenSSF Scorecard.
Q-02 · Q-Trust — Post-quantum cryptography migration as an actual pipeline, not a slide deck: scan your cryptographic estate (CBOM), score it against NIST & CNSA 2.0, plan the migration with a GNN, then seal tamper-proof attestations onchain — 11 UUPS registries on Base L2.
Eating commits since day one. Auto-regenerated by .github/workflows/snake.yml — no manual work, ever.
⌨️ LANGUAGES
🗄️ DATABASE ENGINES
🔐 PROTOCOLS & SECURITY
⚙️ INFRA & TOOLING
- 🟢 ACTIVE QUEST — Hardening the OCPP 1.6J gateway: edge cases, reconnect storms, firmware-update flows.
- 🟢 ACTIVE QUEST — Expanding Q-Trust CBOM coverage across deeper dependency trees and more language ecosystems.
- 🟡 SIDE QUEST — PQC handshake benchmarks on commodity hardware (numbers or it didn't happen).
- 🔵 CO-OP SLOT OPEN — Building something that must not fail? My DMs are open.
The fastest co-op invite is a direct one.
