Selected work / Not a repository dump
A curated set of systems and engagements showing how I think: start with the useful outcome, expose the important constraints, and build the controls needed for the work to survive reality.
01 / Operational transformation
Working inside the operation—from discovery and migration through adoption and controlled delivery.
Manufacturing · dealer systems
Designed and proved an isolated migration path from a legacy dealer quotation platform to a modern serverless architecture.
Property · research to operating action
Connected source-based research, campaign operations, task systems, attribution and human-controlled automation around live commercial activity.
02 / Enterprise delivery
Long-lived software in regulated, offline and operational environments.
Accessible product modernisation
Long-lived mobile and web product work supporting safer bathroom-access decisions, modernised across .NET, MAUI, web and cloud.
Australian Government delivery
Designed and implemented automated unit, integration and cross-platform UI-testing systems, established continuous integration and trained developers and testers to maintain the capability.
Mining · offline field operations
Modernised explosives-inventory applications from Xamarin.Forms to .NET MAUI for high-consequence mine-site operations with intermittent connectivity.
03 / Technical builds
Supporting technical depth, separated from the primary employment evidence.
Browser intelligence
Turns rendered web pages into compact, structured context for AI tools—locally, with deterministic extraction beneath optional on-device intelligence.
Agent infrastructure
A sandboxed MCP orchestration layer that lets AI clients compose tool work while returning only the result that matters.
Native macOS systems
A coherent display command centre spanning hardware DDC, built-in panels, XDR, scenes, automation and failure recovery.
Verified market tooling
Read-only market-data and chart tooling with explicit execution boundaries, bounded history and provenance-aware outputs.
A note on evidence
Some of the strongest work is client-owned or commercially sensitive. I use those repositories to verify my own experience, not as permission to publish code. Where a repository is public, it is linked. For private work, I can discuss the problem, my role and safe architectural patterns without exposing someone else’s assets.