I build infrastructure that does more than work—it can account for itself. My interests sit at the intersection of systems engineering, agent security, reproducible measurement, and developer tooling.
|
01 / CURRENT FOCUS Agent systems that fail safely Constrained tools, least-privilege credentials, controlled network access, and evidence for every consequential action. |
02 / DEFAULT MODE Evidence before confidence Benchmarks need context. Claims need boundaries. Unverified results stay visibly unverified. |
03 / BUILDING WITH Rust · Python · Linux Systems software, reproducible research, AI evaluation, and tooling people can inspect and trust. |
|
LOCAL-FIRST AGENT SECURITY RUNTIME A Rust runtime that puts policy, credential brokering, controlled egress, and tamper-evident audit logs between an AI agent and everything it touches.
72 tests · 404 ns policy-decision p99 · alpha / not independently reviewed |
OPEN-SOURCE CONTRIBUTION · AGENTIC REVERSE ENGINEERING Contributed to a project for reverse engineering software with agents, from observed behavior down to native binaries.
Focused on making deep analysis workflows more reliable and usable from the command line. |
|
OPEN-SOURCE CONTRIBUTION · AGENT HARNESS ENGINEERING Contributed to an agent-harness optimisation system spanning skills, memory, security, and research-first development workflows.
Built for practitioners working across Claude Code, Codex, Cursor, OpenCode, and related environments. |
REPRODUCIBLE CRYPTO-MARKET MEASUREMENT Lossless market-data capture, deterministic replay, and honest cost models for research and simulation.
300 / 300 top-of-book checks · live project |
|
ETHEREUM INDEXING, BUILT FOR FAILURE MODES A concurrent Rust indexer with canonical-chain tracking, reorg handling, crash-safe recovery, and PostgreSQL storage.
232 tests · 150 ns/block decode benchmark · live project |
LLM CODE-EFFICIENCY EVALUATION An open reimplementation and extension of the ENAMEL benchmark for LLM-generated code.
13 models · 161 problems · 612 tests · live project |
More experiments: DepLens — testing whether dependency graphs, code usage, and Git history can predict what a change will break.
|
Same input, same output, every replay. Optimisation is only interesting when the system remains explainable. |
If an action cannot be authorised, isolated, or recorded, it should not quietly proceed with weaker guarantees. |
|
Every result has a method, environment, and limit. A benchmark without context is marketing, not evidence. |
Incomplete work, uncertain conclusions, and known failure modes are part of the engineering record. |



