01 / Work
Agency work · Personal software
My client work was delivered through agency teams. The projects below show the software I build and use outside that work.
02 / Client work
Engineering, architecture and delivery
A sample of consumer and international B2B platforms where I contributed hands-on engineering, architecture, delivery systems or applied DevOps.
Delivered through Vorttex
Frontend, WordPress and Drupal delivery across food, social impact and corporate communications.
Delivered through Airfleet
WordPress engineering, integrations, architecture, delivery systems and applied DevOps across business-critical platforms.
The agencies hold these client relationships. Delivery attribution and trade mark ownership are documented in Legal & privacy.
03 / Systems
Personal products and internal tools
Private operations system · In use
A local-first operations system that combines work evidence, planning data and guarded automation. Management decisions stay traceable and every external write waits for explicit review.
What it demonstrates
Personal product · In development
A web, Android and macOS product that turns read-only financial data into daily guidance. Deterministic code calculates the values. The model receives sanitised results to explain them and has no access to move money.
What it demonstrates
Local financial tool · In use
A local MCP server and CLI that expose read-only Open Banking context to approved agent sessions. Credentials and cached banking data stay on encrypted local storage and payment actions are outside the system by design.
What it demonstrates
Engineering environment · Evolving
A modular working environment for research, implementation and review across local projects. It combines model routing, browser tooling, reusable instructions and persistent project memory without making one provider the source of truth.
What it demonstrates
04 / Method
Patterns shared across the systems
01
Money, permissions, totals and safety rules stay in code. Models work from bounded inputs and cannot replace the source of truth.
02
High-impact changes are previewed, explained and approved. Automation removes repetitive effort without hiding the decision.
03
Credentials and sensitive records are available only to the components that need them. The model receives only what the task requires.
04
Outputs carry their source, confidence and review path. Independent checks matter more as the cost of a wrong answer increases.
05 / Contact
Website support · Integrations · Technical advice
Tell me what you’re working on and where you need help. I’ll reply by email.