W'A.I ENGINELIVE//  W'A.I OS 2.0 ORIGIN 54.8831° N, 1.4809° W  ·  OPERATING FROM LONDON
W'A.I Ask the Engine
← Back to deployed work
W'A.I // SYSTEM READOUT
DivisionBuild
ClientCentre for Economic Security
RoleSoftware, risk analysis plugins and boardroom scanning tools
StatusW'A.I client · April – December 2025 · five builds

Economic warfare tooling

Five instruments built across nine months, from a WordPress plugin that scores company risk from open data to a scanning tool designed to be run live in front of a boardroom.

This was the first iteration of the work that became The Monitor and Primacy, the instruments built before either had a name.

W'A.I client · April – December 2025 · the first iteration of what became the Monitor

SYS.01 Objective

Economic security is an argument about things that have not happened yet, which makes it very easy to talk about and very hard to demonstrate.

A think tank in that field needs instruments, things a reader can operate, that turn its analysis from a claim into an output. The work below is that: not papers about risk, but objects that compute it.

SYS.02 Creative response

Design and build, in PHP and JavaScript, deployed into the client's WordPress estate.

The five builds

  • Live Risk Analysis plugin (April 2025). WordPress and PHP, scoring company risk from open online data, with a front-end pulling results into an Elementor block
  • AI Geopolitical Risk Mapping (May 2025). Risk rendered geographically
  • Economic Warfare Scanning Tool (July 2025). Built for a boardroom panel: interactive, real-time, with generated threat scenarios as discussion points and printable results for handouts
  • NATO Geopolitical Threat Monitoring plugin (July 2025)
  • Economic mapping engine (December 2025). Regional and company-specific threat modelling: the Arctic, African uranium, US semiconductors

Design decision

The Economic Warfare Scanning Tool was built with a mock mode: a flag that lets it run convincingly on generated data, with live APIs wired in behind the same interface later.

That is not a shortcut. A tool that has to be demonstrated in a room full of senior people cannot be one live API outage away from embarrassment, and building the demonstration path first is what makes the real one safe to add.

SYS.03 The five builds

  • Live Risk Analysis plugin (April 2025). WordPress and PHP, scoring company risk from open online data, with a front-end pulling results into an Elementor block
  • AI Geopolitical Risk Mapping (May 2025). Risk rendered geographically
  • Economic Warfare Scanning Tool (July 2025). Built for a boardroom panel: interactive, real-time, with generated threat scenarios as discussion points and printable results for handouts
  • NATO Geopolitical Threat Monitoring plugin (July 2025)
  • Economic mapping engine (December 2025). Regional and company-specific threat modelling: the Arctic, African uranium, US semiconductors

SYS.04 One design decision worth naming

SYS.05 The work

CES launch White Paper
FIG. 01CES launch White Paper
CES launch White Paper
FIG. 02CES launch White Paper
More for Centre for Economic Security

CES · CES membership · The Monitor · CES, the Bush House rebuild · Future of Security

Got one of these?

Build the instrument, not the argument

Anyone can publish a view on risk. Fewer can hand you something that measures it.

If this looks close to something you are dealing with, the quickest route is to say so in a sentence. You will get a real reply from a person, usually with a first read on the problem rather than a calendar link.

Email about work like this Ask the engine first More Build work