The portfolio projects, drawn out. Each diagram shows the mechanism rather than the inventory: what triggers the processing, what crosses a boundary, and where the checkpoint sits before an action reaches the real world.
Diagrams that come from client work are generalised: instances, repositories, channels and modules are named by function.
From a monolithic estate to modules: an isolated control plane, shared building blocks pooled in one place, and a single module contract across three clouds.
3 diagrams → Tooling · CIProving a refactor changes nothing: two branches, two plans, one normalisation, one strict comparison layer by layer.
2 diagrams → AutomationA Slack bot with no exposed URL, four status workflows, and human approval gates before every production release.
2 diagrams → Security & accessNo standing access any more: the tunnel only exists once a human has said yes in Slack, and every open connection is flagged.
1 diagram → Data · SecurityCleartext data never leaves the admin instance: it is anonymised in place before it travels on to staging.
1 diagram → MonitoringThree collection channels carrying distinct payloads into a single platform, plus an infrastructure agent that covers the whole database estate.
2 diagrams →AWS waste is detected read-only; of the three execution paths, only one writes — and only behind an opt-in role.
1 diagram → Agentic AIFive agents hand over to one another on the same Gmail inbox, and the chain stops until a human has reviewed the reply.
1 diagram → Agentic AIOne webhook per conversational turn, a loop that goes back through telephony every time, then the order leaving the voice channel for WhatsApp.
1 diagram →