Status
SteamPeaks
ChartsSalesUpcomingPatchesNewsCalculator
New on SteamEvery app, DLC and depot the minute Steam creates itAppsEvery app on Steam, newest change firstPackagesSubs and bundles, and what each containsDepotsDepots, manifests and install sizesTagsSteam's user tags and the games under themDevelopers & publishersCompanies and their cataloguesTechnologiesEngines, SDKs and anti-cheat found in the filesChange historyEvery PICS changelist as it lands
SignalsNineteen readings of the whole catalogueCompareAny games side by sideRecordsAll-time peaks and the days they were setReportsWeekly and monthly write-upsAlerts & newsroomWatch a game, get told when it movesSteam statusIs Steam up, right nowWeb API explorerTry the endpoints in the browser
NewsSteam's own announcements and the sales calendarCalculatorWhat a Steam account is worth, and its pile of shame
/
Sign in
/
SteamPeaks
The ultimate resource for Steam data.
ExploreChartsSalesSales and festsUpcomingPatchesNewsRecordsTrendingSignals
DatabaseAppsPackagesDepotsTagsDevelopersTechnologiesChange history
ToolsCalculatorCompareSearchAlertsSteam statusAPI
SiteMethodologyFAQDiscordSupportSign in via Steam
Not affiliated with Valve or Steam. Game names and artwork belong to their owners. All times UTC.
PrivacyCookiesFair useStatus
Kepler ProtocolNewsOrdo Arachnis — Where Command Ends
Community

Ordo Arachnis — Where Command Ends

Kepler Protocol · published 25 May 2026, 10:52 UTC

All newsPlayers around this dateRead on Steam

When the enemy has no mind yet still decides.

In a test round of Kepler Protocol, an Imperial reconnaissance patrol observed a swarm-pack two fields away. The pack was heading north — direction clear, pace steady. Then, mid-movement, it turned west. No visible cause. No order from anywhere.

We searched the log for a directive. There was none. There was a gradient instead: a few fields further west the pheromone concentration had shifted the previous turn — a spore plain had burnt out. The pack did not know about it. It followed an incline in the local field. That is not a decision in the human sense. It is not chance either. It is a third thing, and we are still looking for the word.

Classical game AI builds decision trees: if-X-then-Y. That works for an army with a general staff. It does not work for a swarm. We had to start over.

Where we learned it

**Hölldobler and Wilson, The Superorganism, 2008. Two myrmecologists, one life's work, one thesis: eusocial insect societies — ants, termites, bees — are not aggregations of individuals. They are a single organism whose cells are loosely connected through chemical fields. There are no commanders**. The queen lays eggs; she commands nothing. What the colony does emerges from thousands of local decisions that orient themselves on traces left by others.

Pierre-Paul Grassé coined a word for this in 1959: stigmergy — work that triggers other work, mediated by traces in the world, not by direct communication. A termite placed a clump of mud where one already lay, because the pheromone marker was stronger there. That is how the mound was built. No one planned it. No one had to.

For a swarm AI the productive question shifts: not what is the swarm thinking, but what field lies before it and which gradient is it following.

Built

We do not build a decision tree for the Swarm's AI. We build a pheromone field.

Across the whole world there is a pheromone field — a chemical grid over every terrain tile, growing through the Swarm's activity and decaying over time. Brood nodes emit passively. Swarm-packs leave traces while marching. When Imperial troops hunt or build, that too shows up in the pheromone field as friction. A pack reads its immediate surroundings and follows the gradient.

Three drives act in parallel, not in hierarchy:

  • Brood defence — queen nearby? Field pressure rises around her.

  • Tunnel growth — open expansion available? Outward pressure.

  • Imperial reaction — pheromone build-up where Kaiserreich troops have been tips the region into higher arousal.

Each drive carries its own weight per region. The dominant drive shapes behaviour locally. No pack knows what the Swarm is planning. It only knows what its field looks like on the ground. That is enough.

On top of this sits a slow phase mood of the swarm as a whole: dormant → curious → alerted → war. That is not an order; more of a register — like microphone hiss changing as a room fills up. Phase shifts happen over rounds, not in a single action.

Three weeks of work. Not a single central decision point in the code.

In play it shows up as an enemy that does not stop moving when you ignore it — and that sometimes goes exactly where you least expected.

Lore vignette

Two hundred thousand years ago a pre-civilisation on Kepler-186e ended abruptly. What it left behind is in the rock walls: smooth-melted boreholes, geometrically precise, nameless. What it did not leave behind directly lives on in the pheromone fields above the spore plains: Ordo Arachnis. By Linnaean count, eight-legged — therefore spider. That is what we call it.

Captain Ehlers writes in Codex 891.3: "We treat the Swarm as an enemy because we have no language for what it is. But enemy* presupposes that both sides recognise the conflict. The Swarm recognises nothing. It is here, the way the highland is here. We are fighting against geography."*

Next devblog

The Core Drill. For seventeen thousand games it stayed silent — not a single activation in our logs. This week we found out why. And it was not the mechanic. It was two voices that were not speaking to each other.

Stay with us

Wishlist on Steam: Kepler Protocol

Early Access: November 2026

Next devblog: The Core Drill — seventeen thousand games of silence


Kepler Protocol — 4X strategy on a foreign planet. Discipline against the Swarm. Codex against pheromone. A red sun over both.

More from Kepler Protocol

Other announcements

All news
Community22 Aug 2026Six out of Twenty-NineFor two devblogs running we promised the same thing: the drill is next. Here it is. It no longer wins on its own — but it no longer loses unnoticed either. The Empire can win on Kepler in three ways. It can hold out for seventy turns until the fortress stands. It can storm the Alpha Nest — get in, strike down the queen, hold for three turns. Or it can fire up the planetary core drill and settle…Community2 Aug 2026We're joining Next Fest — and taking more time for the launchIn October you can play Kepler Protocol. In November you can buy it. Two pieces of news that belong together. The first: a demo in October Kepler Protocol will be part of Steam Next Fest, 19–26 October. For one week there'll be a playable demo — the landing on Kepler-186e, the first scouting moves, building a colony under a red sun. For us that's the more important half of this announcement. So…Community31 Jul 2026The Army Nobody Saw DieWe spent a night playing 540 games against ourselves. What we were looking for, we didn't find. What we found was worse. Kepler Protocol isn't only tested by hand. We have a second system that plays the game when nobody is watching: two AI sides, the full rulebook, real maps — and a log that records every turn. Every resource level, every march order, every crisis. On the night of 31 July, that…