// About
The person who scopes the work is the person who writes the code.
No account layer, no handoff to a team you've never met. You talk to the person accountable for how it behaves in production.
// Background
Security first, then everything else.
My background is cybersecurity, and it shapes how I build: data boundaries, permissions, and failure behavior get decided at the start, not bolted on before launch.
Since then I've built backend services, data layers, and AI features across production Azure and AWS environments. Most AI projects fail on the ordinary software around the model, not the model itself - so that range is the point. I take on a few engagements at a time, on purpose, so the work stays legible.
Security-first engineering
Threat thinking applied to workflow design - what the system can reach, what it can do unattended, and what it must never do alone.
End-to-end delivery
Infrastructure, backend, data, AI layer, and the interface people actually touch - one person accountable across all of it.
// How I work
Commitments, stated plainly.
- I'll tell you when a workflow isn't worth automating
- I write down what a system can't do, not just what it can
- Acceptance criteria come before implementation
- You own the code, accounts, and credentials
- Any engagement can end without leaving you stranded
- No claims about uptime I can't honour
Do not ship autonomy you cannot defend.
Want to see if this fits?
Start with five focused days to test the risky assumptions and leave with a written scope of work.