Systems architect · Platform engineer
I design secure, repeatable cloud platforms, model their economics, and ship the products that run on them.
DUNEDIN, NEW ZEALAND
I’ve spent more than twenty years designing software systems across commerce, resource planning, and healthcare. Along the way I’ve led technical teams, shaped delivery, and helped organisations make architectural decisions that survive beyond individual projects.
Across all of it, the constant has been the systems behind the software: the decisions, constraints, and trade-offs that determine whether an idea survives contact with production.
My path into software wasn’t conventional. I’m largely self-taught, and my career has been built by designing, building, and operating real systems. That habit of learning by doing still shapes how I approach architecture today.
Fieldstate is my architecture practice and engineering portfolio. It’s where I publish the standards, reference implementations, tools, experiments, and products that grow out of my day-to-day work. Some become commercial products. Others remain open reference implementations. All of them exist to test ideas against reality rather than leaving them in slide decks.
AI-native engineering has changed how I work, while making sound judgement, clear guardrails, and deliberate system design more important than ever.
An LLM gateway that gives you a managed agent — sessions, memory, tools — over any provider. You write against one contract instead of one API per provider: where a provider lacks a managed-agent capability, Loom supplies it rather than flattening every provider down to a shared completion API. The contract is OASP, the Open Agent Session Protocol, and Loom is its reference implementation.
An opinionated approach to solution architecture, and to how products get delivered. Decisions and C4 diagrams live as plain files in the repo, no database, reviewed in pull requests like everything else. It’s the environment I use to design systems, capture architectural decisions, and build reference implementations. The demos are real working architectures, beginning with platform economics and the cost models behind them.
Point-of-sale for community venues: Rust and Tauri on Raspberry Pi kiosks with integrated EFTPOS, live with a paying customer. Built as a social enterprise. I take no revenue from it.
An event-sourced world simulation engine where nothing is scripted. The world advances through replayable events, AI drives its inhabitants, and a Unity client renders whatever emerges.
A generative music engine headed for the browser. Strings are physically modelled, drums are synthesized from primitives, nothing is sampled. It plays endlessly and never repeats itself.
Currently: preparing AZ-104 and AZ-305, open-sourcing the Fieldstate portfolio, and writing up each project. Open to principal platform, solutions architecture, and development manager roles, in Dunedin or remote.