When Machines Read

Chapter 1: AI as the Unforgiving Reader

A CTO commissions an AI reconciliation of strategy documents, architecture models, and code, and receives a calm, precise enumeration of contradictions the organisation had been absorbing socially for years. The CEO’s response is to suppress the output.

A large European telecoms operator pilots an AI assistant for its technology leadership. The brief is modest: given the strategy documents, architecture diagrams, and code, produce a summary of the technology landscape and its alignment with stated strategic priorities.

The CTO is supportive, and a small team feeds the assistant the annual strategy deck, the technology vision document, the architecture reference model last updated fourteen months ago, the service catalogue, and read access to the primary repositories. The assistant produces a twelve-page synthesis that is calm, precise, and specific.

It notes that the strategy deck identifies “digital self-service for enterprise customers” as a top-three priority, but that only two of forty-seven services have any self-service provisioning logic, and both are experimental prototypes with no production traffic. It observes that the reference model describes eight distinct areas of business responsibility, each meant to own its data, while the actual system is organised around legacy databases rather than business domains, with fourteen services sharing a single database. Rather than editorialising, it reads what the organisation claims alongside what the code shows and lists the contradictions.

The CTO recognises every finding; none of it is new to him. What is new is that the confirmation is documented, enumerated, and produced by a system that did not attend a single meeting, in a single document generated in hours rather than months, impossible to dismiss as one person's opinion.

He forwards it to the CEO, who responds within a day, asking that it not be shared further, because “the board narrative is different, and we are not ready to reconcile.” The CTO proposes a compromise, reconciling one business domain, network provisioning, as a limited pilot. The CEO declines: the pilot would produce artefacts that contradict the strategy deck going to the board in three weeks. The objection is not that reconciliation is premature but that it would produce evidence.

The synthesis is saved in a restricted folder, the pilot is called “promising but premature,” and the strategy deck goes to the board unchanged, describing an organisation the synthesis showed does not exist. The CTO now carries two things he did not before: structural confirmation that his reading of the system was correct, and confirmation that the organisation prefers to govern through narrative rather than reconcile reality. He will present the strategy deck unchanged next month, and when a board member asks about self-service progress, he will cite the two prototypes and not mention the synthesis. His technical judgement and his institutional role now point in opposite directions, and he knows which one has authority. The CEO's decision was not to defer reconciliation but to prevent it: narrative coherence preserved at the expense of reconciled evidence.

...

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