Introduction

AI’s most consequential capability is not generation but reconciliation: the ability to read strategy, architecture, and code together and surface the gap between narrative and reality. For most organisations, the synthesis collapses into contradiction.

When a machine can read what an organisation says alongside what its systems do, the organisation's claims become testable. A strategy document can be compared against the code that must implement it; a budget line against the operational outcomes it was meant to produce; a portfolio label against the services that supposedly comprise it. Structural honesty becomes measurable rather than aspirational.

Boards cannot govern without narrative. Narrative is not the enemy; narrative without a test is. Every material claim should be traceable to a process, a named owner and operational evidence—and corrected when the three diverge.

Reading is only the beginning. Organisations are deploying autonomous agents to act within their systems, and those agents require the same preconditions: processes defined explicitly enough to follow, boundaries clear enough to respect, ownership unambiguous enough to navigate. An agent deployed into a structurally incoherent organisation either fails at every boundary where a human previously compensated through social negotiation, or reproduces the incoherence at machine speed.

A software-dependent corporate is a large, established organisation whose products and operations depend critically on software, but whose governance structures were designed for a world in which software was a support function. Banks, insurers, retailers, logistics firms, airlines, public sector bodies, and older companies that call themselves technology companies but still operate with inherited governance assumptions all fall into this category. Between roughly 2008 and 2012, software stopped being infrastructure and became the primary medium through which these companies create and deliver value; the technology changed, but the governance structures, budget cycles, and power structures did not, and the misalignment has been compounding ever since. The most reliable diagnostic is linguistic: if your organisation talks about “the business” as a group of people who are not engineers, it is a software-dependent corporate.

The category includes private-equity-backed companies, where the argument applies at both ends of the investment: the deal team encounters structural dysfunction as a valuation risk in due diligence, and the operating partner encounters it as the primary obstacle to value creation afterwards. The governance levers differ: shorter decision cycles, direct economic incentive, sharper accountability, but the structural diagnosis is the same.

The intended readers are the people who govern software-dependent corporates: members of boards and supervisory boards, particularly non-executive directors and audit committee chairs; and executives, including the CEO, CFO, and CHRO. It is also for the CTO who needs to hand it to them. The technical specificity here, microservices, API contracts, data models, deployment pipelines, is the argument: a board that cannot follow the mechanism cannot authorise the correction. For a non-executive director, the argument carries an additional register, because the board that governs through untested representations when testing is cheap and available occupies a different position from the board that lacked the tools. Closing that gap before it hardens into a discoverable governance record is the work that remains.

...

See also: Full contents · Preview chapters · Illusions of Work