Notes from the architecture desk.
How we design automation and agentic systems that hold up in production: patterns, checklists and the trade-offs behind them.
Hub-and-spoke agent architecture: how to build multi-agent systems that stay explainable
A hub-and-spoke architecture puts one orchestrator in charge of planning, routing and verification, and gives every specialist agent, tool and human reviewer a bounded job. Here is how the pattern works, when to use it, and the design rules that keep it safe in production.
Read → MCP & toolsDesigning MCP servers and tools that agents can use safely
MCP gives agents a standard way to call tools, but a badly designed tool is still a badly designed tool. These are the rules we use for tool contracts, permissions, error handling and logging when we build Model Context Protocol servers for company systems.
Read → Process automationFrom manual process to automated flow: an architecture playbook
Most automation projects fail before the first model call, in the mapping and the boundaries. This is the sequence we use to take a process like invoice intake or support triage from hours of manual work to a running system with humans only where they matter.
Read → Agentic systemsHuman-in-the-loop for agentic systems: where people belong, and where they only slow things down
"Keep a human in the loop" is easy to say and usually done badly: either every step waits for someone, or nothing does. This is how we decide which decisions get a human checkpoint, how the checkpoint is built so it is actually used, and how the loop shrinks over time without losing control.
Read →