Builderofresilientsystems.
Engineer who takes a problem down to the primitive it is missing and builds that. Orchestration and verification harnesses that make an autonomous agent prove its work rather than report it. Cryptographic systems that stop a public ledger from naming who paid whom. Settlement backends where a retry is theft and there is nothing to roll back. Retrieval and data pipelines inside a bank's asset and wealth management division, where the bottleneck was never the model. Rust, Go, Python and TypeScript across five runtimes, most of it owned end to end from the contract up to the dashboard.
EDIT · 2026-09-25
I do not write code to chase trends. I write systems that outlive the cycles they were deployed in. Software that holds together on the worst day, not the best one.
A verification loop wrapped around a coding agent: twelve phases, 460 unit tests, a scope guard, a bug memory keyed by similarity, and a real browser driving the feature before any task is allowed to advance. A policy firewall deciding what an autonomous agent may spend before its key ever signs, with the decision anchored where nobody can revise it. Shielded note pools and channel-account rotation, so the most boring path through a payment system is also the most private one. Credit scored across two runtimes and carried between parachains with no oracle in the risk path. Cross-border payroll formed and swapped along a payment path, where a retry is theft. Different problems, one bias: toward the boring, exhausting middle of the stack.
Sole builder on two of these, lead architect and engineer on the rest, and sole technical owner of the payment infrastructure at the one that became a company. A summer inside JP Morgan Chase, asset and wealth management, where the problem was retrieval rather than consensus and the fix was a Python service that took bug triage from a week to a day. Stellar SCF grantee, open campus incubation, five hackathon wins. The shape of the work is the same every time: own it from the protocol or the contract up through the service layer to the dashboard someone actually looks at, then write up what it taught from the artifacts the build left behind rather than from memory. A ninth system is in active development.
Two systems. Owned end to end.
A policy firewall that decides what an autonomous agent may spend before its key signs, and a verification loop that makes a coding agent prove its work instead of reporting it. The rest of the range is one page away.
