Blog
Working notes on architecture, cloud infrastructure and AI systems — written as things ship.
A high-traffic visitor platform accumulated five cache layers that each kept their own opinion of time. How one monotonic version stamp made them agree — why freshness is a property of a field, not an endpoint — and how to arrive warm at a checkout you don't control.
One question decides how a governed dashboard is licensed, secured and paid for: when the query reaches Power BI, whose name is on it — the person, or the application?
AgentFlow turns an idea typed into a text box into a repository you can actually run — the architecture that gets from prompt to working project.
A content layer that answers before it's asked — one document as the source of truth, read across every channel the museum owns.
A control-plane seam that turns “which cloud” into a runtime detail — six methods behind one interface, so the platform stops caring where it runs.
Treating the job search as a data pipeline — ingest, assess, shortlist, align — and why the most useful AI hiring tool is the one that gets out of the way.
Building an event backbone around a system that emits no events — the enterprise pub/sub integration pattern behind the museum's content estate.
Governed Power BI embedded inside our own React app — a relay that owns nothing, brokering access without holding state or data.
How we connected Auth0 to Tessitura TNEW ticketing with nothing but a post-login hook and a REST call. As far as I can tell, the first time it has been wired this way in Australia.
The architecture of myAI — a git-versioned memory layer, a specialist agent fleet, an autonomous off-hours runner, and an MCP gateway that ties them together. How it works, why it's shaped this way, and where it could go.
The architecture of Connect — an installable support hub where a bug report becomes an AI-triaged, human-approved, autonomously-built fix with a live public timeline. The triage→fix loop, the safety model, and how a year of plans reshaped the ambition.