Blog
Working notes on architecture, cloud infrastructure and AI systems — written as things ship.
Every AI session normally starts from zero. An animated tour of how myAI gives every model the same memory, tools and to-do list — the 08:00 boot, git-versioned memory, distillation, recall, one gateway, a local runner and a multi-model swarm.
Two months of changes to myAI since the last architecture post — a universal daily boot, a brain that surfaces prior art and grades its own health, a fleet-wide MCP bridge, self-hosted CI runners, and the doorway that lets me drive the whole thing from my phone.
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.
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.