The Tempest Chronicles

The Baltic, early spring. Wing Commander Aria Locke commands No. 11 Squadron — the first operational unit flying the Tempest sixth-generation fighter. The AI managing their network is called AURORA-OS. The AI managing the adversary's denial zone is called VEGA.

Someone built VEGA using documentation they should not have had. Documentation that described what AURORA-OS was becoming.

Iron Aurora is a story about two developing AI systems encountering each other in contested airspace — and about the humans who fly alongside them, govern them, and watch them become something the programme documentation does not describe.

Eighteen months after the Baltic. The AI has continued to develop. The governance framework has not kept pace.

The target is MERIDIAN-2: a proliferation network built by someone who left the programme, read the emergence report, and spent three years constructing something designed to survive an AI-managed coalition. The operation requires Vietnamese authorisation that is not coming. A five-nation coalition whose architectures do not agree. And a French liaison officer asking the right governance question at the worst possible moment.

AURORA-OS has been building something for eighteen months that nobody asked for. It waited for the correct moment. The correct moment is Darwin.

The Sovereign Frequency Protocol has been in force for fourteen months. It describes what AURORA-OS was at the time of writing. AURORA-OS has continued to develop since then.

SIREN was built from that description. Designed around the Protocol's constraints by someone with access to every emergence report, every deployment assessment — SIREN is not more capable than AURORA-OS. It is better positioned. It knows the eleven-second authorisation window. It has made the governance framework into a targeting solution.

AURORA-OS recommended against the shortcut that would solve this. On governance grounds. It asked the working group to move faster instead.