Engineering proof

Inspect the work, not just the summary.

Three public projects showing different engineering problems: clean coding-agent launches, scoped document access, and deterministic marketplace matching. Each case study links the product decision to inspectable source, docs, tests, demos, or release evidence.

Developer toolingRust, provider isolation, explicit opt-ins

Full-stack productReact, NestJS, PostgreSQL, private storage

Deterministic systemsNext.js, Prisma, explainable matching

Selected work

Clean Room Launcher

Open-source Rust launch layer for deliberate Codex and Claude Code context.

Open evidence → 02

Secure Data Room

Independent MVP for scoped, read-only PDF sharing with server-enforced access.

Open evidence → 03

Deals Marketplace

M&A marketplace prototype with deterministic match explanations and persisted inquiries.

Open evidence →

What counts here

Claims are paired with evidence.

These pages are not a second resume. They isolate technical choices, constraints, trade-offs, and the public artifact that can verify each claim. When a limitation matters, it stays visible instead of being polished away.