https://monowai.com/writing/ Essays on delivery architecture, contract-first design, and what has to be true before AI takes on the work. en Fri, 30 Oct 2026 00:00:00 GMT https://monowai.com/writing/archify/ https://monowai.com/writing/archify/ A tools note. Archify reads the Markdown that documents a home network and a multi-repo codebase and draws opinionated diagrams shaped by the question asked - a topology, an overview, an unprompted sequence diagram. Where it is gappy, the gap belongs to the documentation, not the picture. Mike Holdsworth Fri, 30 Oct 2026 00:00:00 GMT https://monowai.com/writing/delegate/ https://monowai.com/writing/delegate/ The loop, run as a pre-flight. Versioned inputs, an executable definition of good, evidence by default, an owner - the properties that make a pipeline trustworthy are the ones that make an agent trustworthy. Seven questions, each mapped to the step that answers it, and what it costs when the answer is no. Mike Holdsworth Wed, 23 Sep 2026 00:00:00 GMT https://monowai.com/writing/next-codebase/ https://monowai.com/writing/next-codebase/ The amplification argument one level up. An organisation is a codebase with people in it, and the seams that were never written down get inferred differently by every agent that meets them. Job descriptions as the artefact already written per role, enterprise architecture as the advocate for automated workflow rather than the approver of builds, and the change review board as the seam to measure first. Mike Holdsworth Wed, 16 Sep 2026 00:00:00 GMT https://monowai.com/writing/contract-permits/ https://monowai.com/writing/contract-permits/ The contracts half of the amplification argument. Agreements at the seams, verified by the pipeline, are the deterministic ends that make a probabilistic middle safe - and, documented, they become the index an agent reasons over. What the query assistant and the spec harness were built on, and three moves for Monday. Mike Holdsworth Wed, 09 Sep 2026 00:00:00 GMT https://monowai.com/writing/ai-amplifies/ https://monowai.com/writing/ai-amplifies/ An optimist's case for sequencing. Agents will take real work off engineers and some of it should go today - but delegating before the structure is there just books the cleanup for later, against people who were never asked. The median architecture, MicroContext, and the two questions that survive delegation: which capability, and how the function operates. Mike Holdsworth Wed, 02 Sep 2026 00:00:00 GMT https://monowai.com/writing/contracts-earn-trust/ https://monowai.com/writing/contracts-earn-trust/ Versioned, executable contracts that evolved from test specs into trusted architectural assets delivered as a hands-on workshop that turns integration into an architectural style teams can make their own. Mike Holdsworth Mon, 01 Sep 2025 00:00:00 GMT https://monowai.com/writing/product-domain/ https://monowai.com/writing/product-domain/ Where you draw service boundaries and responsibilities decides who pays for complexity. "Let the API handle it" only works when the API actually owns the domain - core engine, domain service, versioned SDK, end-to-end verification. Mike Holdsworth https://monowai.com/writing/delivery-architecture/ https://monowai.com/writing/delivery-architecture/ Treat delivery as something you architect, not something you push harder on. The System Version, the platform as a product, governance made evidence-based. Mike Holdsworth https://monowai.com/writing/regulated-cicd/ https://monowai.com/writing/regulated-cicd/ Enterprise CI/CD where approvals are permanent and push-to-production is never coming. The gate isn't what disqualifies you from continuous delivery - the manual labour either side of it is. Mike Holdsworth https://monowai.com/writing/regulated-ci/ https://monowai.com/writing/regulated-ci/ Continuous Integration under regulation: branch age as a status, merging unfinished work safely, and what a build must guarantee before anything leaves it. Mike Holdsworth https://monowai.com/writing/regulated-cd/ https://monowai.com/writing/regulated-cd/ Promoting one artefact through four environments past a human decision, without a person performing the deployment. The deployment contract, freezes, rollback, retention, and the seam. Mike Holdsworth