Loom
design essayA managed-agent gateway built around one contract across providers. The project essay explains why Loom supplies missing capabilities instead of reducing every provider to a shared completion API.

Systems architect · Platform engineer
I work on the decisions behind software: how a system fits together, what it costs to run, and how an idea becomes something people can use.
DUNEDIN, NEW ZEALAND
Architecture, engineering and the decisions that connect them. A place to explain the problem, the alternatives and why a particular approach makes sense.
EXPLORE WRITING →I’ve spent more than twenty years designing software systems across commerce, resource planning and healthcare. I’ve led technical teams, shaped delivery and helped organisations make architectural decisions that last beyond individual projects.
My work spans system design, platform engineering and the economics of running software. The thread through it is understanding the constraints, making the trade-offs explicit and carrying those decisions through into implementation.
I’m largely self-taught. Designing, building and operating real systems has shaped how I learn and how I work. The projects below give that experience a concrete form; the writing makes the reasoning behind them easier to follow.
PROFESSIONAL BACKGROUND · LINKEDIN ↗Projects that put the ideas into practice. Start with Loom for a detailed design essay, or explore the shorter project profiles.
A managed-agent gateway built around one contract across providers. The project essay explains why Loom supplies missing capabilities instead of reducing every provider to a shared completion API.
An environment for designing systems and capturing architectural decisions. C4 diagrams and decisions live in the repository, reviewed alongside implementation; reference architectures explore platform economics.
Point-of-sale for community venues, built with Rust and Tauri on Raspberry Pi kiosks and integrated EFTPOS. A social enterprise with a paying customer; I take no revenue from it.
Fieldstate is my consulting practice. It’s where I help teams review AI-built applications, connect architecture to requirements and delivery, and define a solution before engaging a supplier.
For a focused review or help turning a need into a clear brief, explore the engagements at Fieldstate.
EXPLORE FIELDSTATE ↗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.
I’m developing this site as a home for my writing and project work: making the decisions behind the software easier to understand, alongside the work itself.
Through Fieldstate, I’m shaping focused engagements around application review, architecture and traceability, and requirements and solution definition.