Enterprise-Ai on M.F.Bormanhttps://www.mfborman.nl/tags/enterprise-ai/Recent content in Enterprise-Ai on M.F.BormanHugoenMon, 06 Jul 2026 00:00:00 +0000Learned, then ratifiedhttps://www.mfborman.nl/articles/learned-then-ratified/Mon, 06 Jul 2026 00:00:00 +0000https://www.mfborman.nl/articles/learned-then-ratified/A learned system can tell you what your software did. It cannot tell you who is answerable for what that behaviour now obliges you to do.AI made building cheap. It made alignment more expensive, not lesshttps://www.mfborman.nl/posts/2026-06-25-ai-made-building-cheap-it-made-alignment-more-expensive/Thu, 25 Jun 2026 00:00:00 +0000https://www.mfborman.nl/posts/2026-06-25-ai-made-building-cheap-it-made-alignment-more-expensive/AI collapsed the cost of producing code. It did nothing to the cost of agreeing what the code should be derived from. Cheap building raised the value of expensive alignment, not the other way around.The honest near-term picture is a dark workshop, not a dark factoryhttps://www.mfborman.nl/posts/2026-06-23-a-dark-workshop-not-a-dark-factory/Tue, 23 Jun 2026 00:00:00 +0000https://www.mfborman.nl/posts/2026-06-23-a-dark-workshop-not-a-dark-factory/The dark software factory is further off than the noise suggests. A workshop is one bounded bench AI can already run unattended; a factory is governance across owners that no model yet holds.Copilot is a tool; BlackRock rolled a substratehttps://www.mfborman.nl/posts/2026-04-22-copilot-is-a-tool-blackrock-rolled-a-substrate/Wed, 22 Apr 2026 00:00:00 +0000https://www.mfborman.nl/posts/2026-04-22-copilot-is-a-tool-blackrock-rolled-a-substrate/Tools compound linearly with seats. Substrates compound with the agents built on them. That is the structural difference between an AI programme and an AI transformation.Every business function is redesigning for AI, except software engineeringhttps://www.mfborman.nl/articles/the-local-optimum-trap/Wed, 15 Apr 2026 00:00:00 +0000https://www.mfborman.nl/articles/the-local-optimum-trap/When AI entered customer service, nobody said ‘just give the agents ChatGPT and carry on.’ In software engineering, we’re making exactly that mistake.Context maturity governs every value stream, not just codehttps://www.mfborman.nl/posts/2026-04-02-context-maturity-governs-every-value-stream/Thu, 02 Apr 2026 00:00:00 +0000https://www.mfborman.nl/posts/2026-04-02-context-maturity-governs-every-value-stream/Context maturity turned out to be the governing variable for code estates. It may be the governing variable for every enterprise value stream where AI accelerates change.The governance gap AI-driven delivery can't outrunhttps://www.mfborman.nl/articles/the-governance-gap-ai-driven-delivery-cant-outrun/Mon, 23 Mar 2026 00:00:00 +0000https://www.mfborman.nl/articles/the-governance-gap-ai-driven-delivery-cant-outrun/The SDLC isn’t dying, it’s migrating from documents into the execution engine. Most organisations stall at machine-speed delivery under human-speed governance. The missing piece is a function nobody is staffed to own: interpretation binding.Consulting firms are building the wrong muscle for AIhttps://www.mfborman.nl/articles/consulting-firms-are-building-the-wrong-muscle/Sun, 22 Mar 2026 00:00:00 +0000https://www.mfborman.nl/articles/consulting-firms-are-building-the-wrong-muscle/AI is not just changing how work is done. It is changing the rate at which change is proposed. The constraint has moved from strategy to absorption.What breaks when governance becomes load-bearinghttps://www.mfborman.nl/posts/2026-03-17-what-breaks-when-governance-becomes-load-bearing/Tue, 17 Mar 2026 00:00:00 +0000https://www.mfborman.nl/posts/2026-03-17-what-breaks-when-governance-becomes-load-bearing/Moving AI governance into the execution layer is the right structural move. What gets less attention is what breaks when you do it.AI increases throughput, not review capacityhttps://www.mfborman.nl/posts/2026-03-13-the-delegate-and-review-illusion/Fri, 13 Mar 2026 00:00:00 +0000https://www.mfborman.nl/posts/2026-03-13-the-delegate-and-review-illusion/The emerging consensus is to delegate execution to AI and review the output. But review is inspection, and inspection scales with volume. The constraint is the operating model.Failure modes belong in the execution layer, not in documentationhttps://www.mfborman.nl/posts/2026-03-10-failure-modes-as-system-constraints/Tue, 10 Mar 2026 00:00:00 +0000https://www.mfborman.nl/posts/2026-03-10-failure-modes-as-system-constraints/A documented failure mode gets reviewed. A system constraint gets enforced. The difference is whether governance scales with headcount or with the system.The law of authority under accelerationhttps://www.mfborman.nl/articles/the-law-of-authority-under-acceleration/Thu, 05 Mar 2026 00:00:00 +0000https://www.mfborman.nl/articles/the-law-of-authority-under-acceleration/Token Jail is not vendor lock-in. It is what happens when implicit authority meets machine-speed execution. The dependency lives in the operating model, not the API.The constraint on AI delivery is promotion, not codehttps://www.mfborman.nl/posts/2026-02-26-the-constraint-is-promotion-not-code/Thu, 26 Feb 2026 00:00:00 +0000https://www.mfborman.nl/posts/2026-02-26-the-constraint-is-promotion-not-code/AI can generate more change than most organisations can safely absorb. The constraint is not code, it is promotion: a change advances only when it has collected the evidence a gate requires.The compounding pipeline: from novel to deterministichttps://www.mfborman.nl/posts/2026-02-17-the-compounding-pipeline/Tue, 17 Feb 2026 00:00:00 +0000https://www.mfborman.nl/posts/2026-02-17-the-compounding-pipeline/The first time AI solves a migration pattern, it is novel. The second time, a recipe. The tenth time, deterministic. Context maturity is what makes this compound.The seam between exploration and industrialisation is where AI risk liveshttps://www.mfborman.nl/posts/2026-02-17-the-seam-between-exploration-and-industrialisation/Tue, 17 Feb 2026 00:00:00 +0000https://www.mfborman.nl/posts/2026-02-17-the-seam-between-exploration-and-industrialisation/The hardest part of AI in a regulated enterprise is not invention or industrialisation. It is the seam between them, moving work into repeatable execution without losing intent, control, or trust.Context maturity is a capability, not a projecthttps://www.mfborman.nl/posts/2026-02-14-context-maturity-is-a-capability/Sat, 14 Feb 2026 00:00:00 +0000https://www.mfborman.nl/posts/2026-02-14-context-maturity-is-a-capability/AI makes backward context creation feasible at estate scale. What matters is whether attested context exists — the technology is incidental.AI-extracted understanding is a hypothesis, not documentationhttps://www.mfborman.nl/posts/2026-02-12-ai-extracted-understanding-is-a-hypothesis/Thu, 12 Feb 2026 00:00:00 +0000https://www.mfborman.nl/posts/2026-02-12-ai-extracted-understanding-is-a-hypothesis/When AI analyses existing code, the output looks like documentation. It is not. Validation means checking whether an interpretation matches observed reality.Legacy is context maturity, not code agehttps://www.mfborman.nl/posts/2026-02-10-legacy-is-context-maturity-not-code-age/Tue, 10 Feb 2026 00:00:00 +0000https://www.mfborman.nl/posts/2026-02-10-legacy-is-context-maturity-not-code-age/A twenty-year COBOL estate has the same problem as a three-year microservices platform whose team rotated out. The variable is context maturity.