The Regime Map research pipeline
A daily geopolitics and markets brief that cannot publish a number until a separate checker has tried to prove it wrong.
Links
The Regime Map is a daily brief on where geopolitics is pushing capital. More than 100 issues have been published at theregimemap.com since 19 June 2026. Each one is researched, drafted, checked and delivered by a pipeline of AI agents that I designed, and it has to be ready by 8:15 in the morning, Eastern time.
How an issue gets made
One scheduled run produces one brief. An orchestrator does a pre-flight check, then hands the work to four agents in turn. The first gathers the research and records every figure it intends to use in a fact ledger. The second writes the brief from that ledger. The third amends the draft after it has been checked. The fourth renders the issue and delivers it for publication. The checking happens twice, once on the ledger and once on the finished draft.
The falsify gate
The gate is the part I care most about. For every figure the brief's argument depends on, it starts a separate checker whose only job is to show that the figure is wrong. Each checker is sealed off from the others and from the agent that wrote the claim, so it cannot simply agree with the draft.
If a figure that the argument depends on fails, the issue does not go out until it is fixed. Figures that only decorate the appendix are checked but do not block. A refuted value is treated as a dispute to settle, not as permission to overwrite the number with whatever the checker found. When a fix lands after delivery, the issue carries a Corrections block that day.
The gate earns its place. In one audit on 15 September 2026, of 30 claims put through it, 6 were confirmed, 12 needed correction, 11 were refuted and 1 could not be verified.
Rules that keep the numbers honest
- One number, one home. Every figure the argument uses is a reference to a single entry in the day's fact ledger. The prose cannot carry its own copy of a number that might drift.
- Every market figure has a time. A price is a snapshot, so it is shown with the time it was taken, and a forecast is a dated range rather than an undated point.
How it was built
The code is in a private repository. Of the repository's 649 commits made by people rather than by automated jobs, 597 were written with Claude or Codex. My part is the design of the pipeline, the written rules it follows, and the gate that decides what is allowed to ship.