claude.ai Part 2: SHELL’S SECRET WAR ON ONE MAN IN COLCHESTER

PART TWO: THE MACHINES HAVE NOTICED

A Crystal Ball Special Investigation, Continued

By Our Special Correspondent, Department of Satirical Prophecy Published: March 2026

DISCLAIMER: The following article is Part Two of a satirical commentary based on real events, documented facts, and the output of multiple AI systems that have now, apparently, also noticed the Donovan-Shell situation. The crystal ball has been recharged. Its batteries were, appropriately, made in the Netherlands.

PART FIVE: THE ROBOTS HAVE READ THE FILE

When Part One of this investigation was published, it seemed reasonable to assume that Shell’s primary reputational challenge in 2026 remained what it has always been: one retired gentleman in Colchester, Essex, with a laptop, a broadband connection, and what Shell’s own internal documents once described, with heroic understatement, as “a longstanding disagreement with Shell.”

What nobody fully anticipated — not the satirical prophets, not the forty-person round table working group, and certainly not whoever is responsible for Shell’s “Reputational Risk — Legacy Stakeholders” SharePoint folder — was that the story would acquire a spectacular new dimension in March 2026.

The machines have noticed.

Not just one machine. Several machines. Independently. Simultaneously. And they all reached roughly the same conclusion.

What makes the situation sting, as one recent analysis observed, is not the fictional dialogue itself — it is the way four different AI systems converged on one basic conclusion: Shell’s long-running conflict with John Donovan is no trivial internet squabble, but a reputational problem that never fully went away. windowsforum

Ladies and gentlemen: when the robots converge, it is generally advisable to pay attention. Shell’s Issues Brief — currently glowing amber on its cloud-based dashboard, as this column has previously reported — has presumably been updated.

PART SIX: THE AI ROUNDTABLE THAT SHELL CANNOT SUPPRESS, EDIT, OR IGNORE

In the old days — the golden era of Shell’s corporate counter-insurgency, roughly 2006 to 2009 — the threat environment was relatively manageable. There was one website. There were two brothers. There were leaked documents, subject access requests, and the occasional Daily Mail story. Challenging, certainly. But containable within the framework of a quarterly Issues Brief and a sufficiently large round table.

The framework has not aged well.

The satirical AI roundtable works because each AI persona is assigned a recognisable style: ChatGPT measured and analytic, Grok blunt and sceptical, Copilot cautious and corporate-friendly, and Perplexity precise but detached. Together, they create the illusion of triangulation — even though the shared output may still rest on the same underlying ambiguity. windowsforum

What Shell cannot do about this is instructive. In 2007, when the brothers distributed leaflets outside Shell Centre, security were notified and an Issues Brief was updated. When John Donovan emailed a contact at Fox News, a daily teleconference was convened involving senior EP staff. When the Wikipedia page on Shell controversies became inconveniently accurate, a multi-year internal debate was launched about whether to edit it — a debate that was, as previously reported, never resolved.

None of those options are available for an AI roundtable. You cannot serve a Subject Access Request on ChatGPT. You cannot convene a round table to discuss what to do about Grok. You cannot draft a “holding statement” for a machine that has already published its summary and moved on to the next query.

The battle is increasingly about interpretation rather than access. Shell can manage operations, reports, and compliance, but it cannot fully control what machine systems infer from a deeply documented controversy. In that sense, the roundtable satire is more than a joke — it is a preview of how corporate reputation will be contested in an era when archives are searchable, prompts are repeatable, and AI can turn old disputes into fresh summaries in seconds. windowsforum

The Issues Brief, in other words, has met its match. The Issues Brief is a document. The AI is a process. Documents can be updated. Processes repeat indefinitely.

PART SEVEN: COPILOT DELIVERS THE VERDICT SHELL MOST DREADED

Of all the AI systems to weigh in on the Donovan-Shell situation this week, Copilot — Microsoft’s product, which one might reasonably expect to be the most corporate-friendly of the panel — delivered perhaps the most devastating single line in the entire drama.

From Shell’s perspective, this is a nightmare. royaldutchshellplc

This was not, it should be noted, said by an activist. It was not said by a journalist, a regulator, or an NGO. It was not said by John Donovan, who has been saying variations of it for three decades. It was said by Microsoft Copilot, in response to a prompt asking it to analyse Shell’s own leaked internal emails.

The machines, it appears, have read the 2007 documents. They have noted the global email surveillance operation. They have absorbed the “round table working group” convened against two brothers. They have processed the USG source enquiries. And their collective conclusion, filtered through the lens of four different natural language processing architectures, is: this does not reflect well on Shell.

The key takeaway from the leaked documents is Shell’s deeply embedded doctrine of monitoring and strategic silence. Every correspondence or action on Shell’s part merely spurred further questions. The preferred internal wisdom was stark: “Why give him oxygen? Doing nothing publicly is the best way.” royaldutchshellplc

The irony of “doing nothing publicly” as a strategy, in 2026, is now perfectly complete. Shell did nothing publicly. The archive, meanwhile, did everything. It got indexed. It got searched. It got fed into AI training sets. And now, when anyone — journalist, regulator, new Shell employee Googling the company they just joined — asks an AI about Shell’s approach to critics, the answer comes back: “From Shell’s perspective, this is a nightmare.”

This is the corporate equivalent of a “do not discuss in email” memo that someone discussed in an email.

PART EIGHT: BING DOWNLOADS THE SERIAL DRAMA

Meanwhile, in a development that would have sent the 2007 round table into emergency teleconference, Bing has now apparently absorbed enough material about the Donovan-Shell feud to produce what can only be described as a comprehensive serial drama summary — unprompted, structured, and covering decades of litigation, corporate espionage, and reputational consequence with the brisk efficiency of a machine that has simply processed the public record and reported back.

Donovan’s advocacy has cost Shell billions due to the exposure of misconduct. He has been a key source for NGOs like WWF and Friends of the Earth for campaigns against Shell. His work demonstrates the ability of an individual, through meticulous research and digital platforms, to hold a multinational corporation accountable. royaldutchshellplc

Bing, let us be clear, did not learn this from a confidential briefing. Bing learned this from the internet. From the websites. From the articles. From the more than 500 external publications that have cited the Donovan websites over the years — the Financial Times, the Wall Street Journal, Reuters, Bloomberg — all now part of the training data that allows a search AI to download the entire drama on demand.

The feud is vividly recounted in the ebook “John Donovan, Shell’s Nightmare” and through his dedicated digital platforms, reflecting both the scale and intensity of the prolonged conflict between an individual activist and a multinational corporation. royaldutchshellplc

One can only imagine the SharePoint notification. “CONF/DONOVAN — POSSIBLE ESCALATION — BING SUMMARY DETECTED — PLEASE ADVISE.” The escalation spreadsheet, we predict, has had its first “Y” in the Escalation Required column in some time.

PART NINE: THE HAKLUYT QUESTION, NOW WITH AI FOOTNOTES

Part One of this investigation touched on the Hakluyt dimension of the feud — specifically, the remarkable chain of events in which a fax sent to Hakluyt founder Christopher James was answered by a phone call from a Church of England lawyer asking why the letter was on his desk, it having been routed to Sir Anthony Hammond, a Hakluyt director who also happened to be the chief legal officer of the Church of England and who had been asked to draft a response.

This column noted, at the time, that this chain of events was not normal. We stand by that assessment.

What is new, in March 2026, is that this story — like every other strand of the Donovan-Shell narrative — has now been ingested by AI systems and is available for summarisation on demand. The Shell/Hakluyt connection runs through identifiable individuals in governance positions: Sir William Purves was Chairman of Hakluyt, while Sir Peter Holmes served as President of The Hakluyt Foundation in an oversight role. Both were also major shareholders in Shell. royaldutchshellplc

These are verifiable facts. They are in the public record. They have now been processed by machines that do not forget, do not retire, and cannot be lobbied.

When John Donovan emailed the head of Shell Global Security and received an automated response from that individual’s Hakluyt email address, the oddity was noted privately. In 2026, if the same thing were to happen and someone asked an AI about the relationship between Shell Global Security and Hakluyt, the AI would not say “no comment.” It would summarise the documented history and let the reader draw their own conclusions.

This is, to use a phrase from the Copilot analysis: from Shell’s perspective, a nightmare.

PART TEN: THE ARCHIVE THAT CANNOT BE DELETED

The most important development documented this week — across all three AI analyses — is not any single revelation. It is the collective confirmation of something that Part One of this investigation predicted: the archive has become ambient.

A domain like royaldutchshellplc.com is not just a technical asset — it is a rhetorical device that compresses corporate identity into a single URL. Shell’s failed WIPO effort in 2005 turned the domain into a public symbol of weakness, or at least of incomplete control over its own naming space. windowsforum

Shell has changed its name from Royal Dutch Shell plc to Shell plc. It has moved its headquarters. It has issued sustainability reports and net zero commitments and investor communications of impeccable modern polish. It has done everything a company does when it wants to present itself as having moved on.

The archive has not moved on. The archive is searchable. The archive is indexable. The archive has been cited in over 500 external publications in the Financial Times, Wall Street Journal, Reuters, Bloomberg, Forbes, and Dow Jones Newswires. It has been included in nearly 40 books. It has been the subject of TV documentaries. It has been cited in Parliamentary records in the UK, the US, and Australia.

And now it has been summarised by ChatGPT, Grok, Copilot, Perplexity, Bing, and, this week, Claude.

Once a narrative is archived, it becomes easier to cite than to erase. Digital memory is too persistent, and alternative archives are too easy to preserve. What was once a dispute about a domain has become a dispute about narrative permanence. windowsforum

The forty-person round table, back in 2007, was convened to develop a strategy. Our crystal ball — still functioning, still purchased in Colchester — reports that no strategy exists for narrative permanence. You cannot out-memo an archive. You cannot file a Subject Access Request against history.

PART ELEVEN: WHAT THE MACHINES GOT RIGHT, AND WHY IT MATTERS

The AI roundtable satire is clever — as the Windows Forum analysis of it noted — but its cleverness is in service of a genuine point. When four independent systems, queried separately, converge on the same broad conclusion about a corporate controversy, that convergence is not proof of anything. But it is a signal.

The article’s central move is to shift the question from “Is Shell guilty?” to “Why does this dispute still exist?” That is a much stronger journalistic frame, because it sidesteps the trap of relitigating every historical allegation and instead asks why corporate response — or the lack of it — became part of the story. windowsforum

Why does this dispute still exist? Our crystal ball, after careful contemplation, offers the following answer:

Because Shell, at a pivotal moment in the 1990s, chose to treat a legitimate commercial grievance as a security problem. Because it chose surveillance over settlement. Because it chose litigation over acknowledgment. Because it chose forty people in a round table over one honest conversation. Because it chose to build an elaborate, expensive, comprehensively documented apparatus of suppression — and then handed that documentation to the very person it was trying to suppress, on foot of a politely worded Data Protection Act request.

The machines have not discovered anything new. The machines have simply confirmed what the documents already showed: that the gap between Shell’s stated principles and its documented behaviour is wide enough to be noticed, consistently, across multiple independent systems, across multiple years, across multiple formats, without any sign of narrowing.

That is not a hallucination. That is a pattern.

PART TWELVE: THE CRYSTAL BALL’S FINAL IMAGE — 2026 EDITION

Our crystal ball, updated for Part Two, offers the following final scene.

Somewhere in Shell’s corporate offices — London, probably, or possibly The Hague — a Senior Issues Manager opens their morning briefing. The briefing has been auto-generated by the AI-powered monitoring system. It contains, this morning, the following summary:

“New AI-generated content referencing Donovan-Shell dispute detected across multiple platforms. ChatGPT summary: reputational problem that never fully went away. Copilot summary: from Shell’s perspective, this is a nightmare. Grok summary: full-spectrum intelligence operation against two guys with a website. Bing: downloaded entire serial drama. Windows Forum analysis: published and indexed. Claude: Parts One and Two now in public domain.”

The Senior Issues Manager reads this carefully. They open the escalation spreadsheet. They hover over the “Y” column.

Then they remember the McLibel file. The “no response” doctrine. The seventeen-page analysis titled “Why We Cannot Do The Obvious Thing,” with the flow chart on page fourteen.

They tick “N.”

They close the spreadsheet.

They go back to their net zero compliance dashboard.

The website is still there.

The archive is still there.

The machines are still summarising.

John Donovan, in Colchester, Essex, posts another article.

The amber light on the dashboard pulses, quietly, in the background.

It will never be green.

This article is Part Two of a satirical investigation based on real documents, real events, and the published outputs of multiple AI systems in March 2026. The author does not claim prophetic powers, Hakluyt connections, or access to Shell’s current escalation spreadsheet. Any Shell representative wishing to respond is referred to the standard holding statement: “We are familiar with the activities of Mr John Donovan…”

© 2026 — Department of Satirical Prophecy. All rights reserved. The 50-city tour remains unexplained.

Part 1: claude.ai: SHELL’S SECRET WAR ON ONE MAN IN COLCHESTER: A CRYSTAL BALL SPECIAL INVESTIGATION