I build engineering systems that make AI-assisted delivery reviewable.
Senior software engineer focused on the substrate around coding agents — plans, scoped tools, verification gates, and sanitized receipts. Four case studies follow.
AI-assisted delivery becomes reviewable when the engineering system around it is explicit.
Coding agents are fast at producing output. They are slow at producing reviewable output. The difference is not the model; it is the engineering system around the model — the plans, scoped tools, verification gates, and receipts that turn agent activity into something a senior engineer can defend in review.
- 01
Plans are written before execution. Scope, non-goals, and confidence are explicit.
- 02
Agents act through scoped tools whose calls and outputs an engineer can audit.
- 03
Work is only complete after verification has run and its output is recorded.
A path through the reliability narrative.
Four sanitized case studies, ordered from the flagship system to the evidence model that makes the whole thing reviewable.
- Case study 01
AI-Assisted Delivery Reliability System
An engineering system that turns AI-assisted software development into reviewable, repeatable delivery — explicit plans, scoped agent tools, verification gates, and sanitized receipts.
AI engineering Backend / Platform Verification - Case study 02
Agent Tools Workstation System
A reproducible AI engineering environment — scripted setup, shared skills, sub-agent personas, host integrations, and conventions that make a single workstation behave like a small platform.
AI engineering DX Infrastructure - Case study 03
MCP Router
A reliable tool-routing and plugin/runtime platform for the Model Context Protocol — typed surfaces, lifecycle hygiene, plugin isolation, and observable failures.
Backend / Platform Infrastructure AI engineering - Case study 04
Work Receipts Ledger
An evidence model for reviewable AI-assisted delivery — agent sessions grouped into work items, assigned quality bands, audited against privacy guards, and selectively exported as sanitized snapshots.
Verification Security DX
Five proof areas, one reliability thesis.
AI, backend, frontend, infrastructure, and security are not separate pillars in this portfolio. Each is presented as evidence the same thesis can hold under production constraints.
Pick a path that fits the conversation.
Start with the case studies for the long read, or book an open conversation for a 30-minute technical chat.