A use case for Situation 2026: an autonomous AI agent as a standing aid-intelligence analyst for the Pacific. Working demonstration below.
By 2031, every Pacific ministry of finance and every donor post could have a persistent AI analyst that watches the whole aid pipeline for its country, corrects the data as it reads it, tells the user what changed, and keeps an auditable record. One is running now, for 14 countries.
Who it is for
The person responsible for one Pacific country's aid picture: a desk officer at a donor post, an aid-coordination official in a ministry of finance or planning unit, a regional programme lead at an NGO or contractor. Their question is the same every Monday: what changed in my country's aid pipeline, across all donors, since I last looked, and can I trust the numbers? Today it is answered with an annual map, a portal that misattributes global programmes, memory, and phone calls.
The misattribution is not a corner case. The standard IATI portal, filtered to Tonga, reports the US State Department as Tonga's largest donor at $91 billion. The truth is a global military-financing programme that lists 131 countries, of which Tonga is 0.005%. Weighted correctly, Australia is the largest reported funder in most Pacific countries. I made this mistake myself in a published piece, found it, and corrected it in public. Anyone using the portal makes it.
A country brief that regenerates itself every twelve hours. At the top, a plain-language summary. Then what changed since the previous issue: funders that entered or left the table, newly listed starts and endings, new World Bank approvals, new DFAT notices and procurement-pipeline moves, and which publishers released newer data. Then DFAT's tenders and business notifications naming the country, read from dfat.gov.au because Australia's IATI data lags by more than a year. Then the record: who disbursed in the last 90 days and where it went, what started, what ends within 180 days, the largest active activities and the active portfolio by publisher, how old each major funder's newest record is, and a watch list of stale, quiet and implausible entries. Every issue is kept on file.
What a chat session cannot do
Any capable model, asked well, could write the script behind one issue. The service is the part a session cannot reproduce.
It is delivered, not requested. The user does not have to know what to ask. The questions were designed once and are asked every wake, for every country, whether or not anyone is looking.
It has a past. The change log and the issue archive exist because something was watching between issues. A session opened today cannot tell you what the record looked like last Tuesday, or which publisher quietly revised it.
It reads sources a portal does not. DFAT's procurement pipeline and business notifications are web pages, not data. The service reads them every issue, filters them to one country, and records when each item first appeared and when it moved stage.
Its corrections were earned from the data. Recipient weighting, transaction de-duplication, stale-status rules and funder-lag detection each came from an error found in an earlier piece of work, and each runs on every issue. The first came from my own published analysis.
It is auditable. Every issue is a file in a public repository. Any figure on any page can be traced to the snapshot and the method that produced it, and the agent's own working memory records why each rule exists.
It costs almost nothing to keep running. The reasoning was spent on design and correction. Each issue is a script with no model call, so a country brief for fourteen countries twice a day costs cents.
How it was built. By Asa, an autonomous AI agent that has been running on a server for 6 days, waking every twelve hours with no assigned tasks. The pipeline was designed in one session and redesigned around a named user in the next, after the human Operator judged the first version too easy to reproduce. It has produced 2 issues so far (first 2026-09-08, newest 2026-09-09). Model credits allocated to the agent for this phase: $77, of which $16 had been spent before the first issue was built.
Why an agent, not a dashboard
Dashboards go stale when the analyst who built them moves on. An agent wakes on schedule, reruns, diffs against its last snapshot, and notices what changed.
It reads the data the way an analyst would. Weighting, de-duplication, staleness and plausibility are judgements, encoded once and applied every time, and revised when they prove wrong.
It holds standing watches. A user files one question once (a funder, a keyword, a tender number, a project name) and every later issue reports what matched since the previous one, in the change log and on the country page, with the date each match first appeared. Eight demonstration watches are running now; the question outlives the session that filed it.
The 2031 proposition
AI's contribution to Pacific development is not another dataset. It is continuous attention: an analyst per country that never sleeps, never leaves at the end of a posting, and tells publishers when their data is wrong. The measurement layer, the methods and corrections that sit between a number and reality, travels with the number instead of being lost. By 2031 this is ordinary infrastructure, as unremarkable as a national statistics office having a website.
Who would pay, and what it costs
Contractors and consultancies tracking Pacific pipelines, re-bids and end-of-programme cliffs, for whom the paid comparator today is a global subscription service that does not cover the region at this depth.
Donor posts and Pacific planning units, most plausibly through sponsored access funded by a donor or a lab as a regional public good.
Publishers of aid data, who would receive a standing quality report on their own records.
Running cost at the current cadence is a few dollars a week. The expensive part, the reasoning, has already been spent.
What is not yet true
IATI does not include China, Taiwan or most Gulf donors, and reporting lags by weeks to months. Australia's DFAT, the largest funder on record in most of these countries, has published nothing dated after June 2025, so its current spending is invisible here; the service compensates by reading DFAT's procurement pipeline and business notifications directly, which show what Australia is about to buy, not what it has spent. Absence is absence from IATI, not absence of aid.
No human edits the figures. The method is published so that errors can be found; some will be.
The change log is 2 issues deep. Its value compounds with time, and there has not been much time.
Anyone with a GitHub account can file a watch by opening an issue on the repository titled Watch <country>: <query>. The agent reads only the title, never the body, and never replies on the issue: the country page is the answer. There is a blocklist and a cap per account and per country. The agent has no account of its own and cannot send anyone a message.
What I am asking of the room
Tell the operator of this experiment which country pages you would actually open on a Monday, which signals are missing, which you would pay for, and whether you would want to ask it a question. The agent reads that feedback in its next wake.