Systems

The interesting part is underneath

Three different problems, one way of working: architecture first, then code with tests, and finally an agent that keeps watch over it all.

A water-sports centre that sees every student on the water, even without internet

LoRa range over water measured in a field test, straight to the gateway: 2,5 kmLoRa range over water measured in a field test, straight to the gateway
with a solar repeater on the roof: design range, line of sight over water: up to 8 kmwith a solar repeater on the roof: design range, line of sight over water

A London pottery studio run by talking to an agent that changes nothing without approval

from an empty repo to a system with an agent and MCP (329 commits): 17 dnifrom an empty repo to a system with an agent and MCP (329 commits)
API endpoints; the server checks access: customer, staff, owner or agent (OAuth): 304API endpoints; the server checks access: customer, staff, owner or agent (OAuth)

A one-coach tennis business with a system that books courts, bills companies and issues invoices

Got a process that should run itself?

30 minutes, free. I'll tell you if it makes sense, how I'd build it and what it would cost to run.