ALTINERISRequest access
  1. I01RULE SHIFTERS
  2. I02429 SWARMLINGS
  3. II03CLAIM CRAWLERS
  4. II04MIMIC WARDENS
  5. III05GREY FOG
  6. III06THE FUNNEL
  7. IV07PUPPETEER HUNTERS
  8. V08INFRINGER LEDGER
Threat file 02 · rate-limit exhaustion

THE ENEMY THAT IS YOUR OWN TRAFFIC

Swarmlings are the strangest species in the bestiary: they are your own automation, turned feral. Every background poll, retry loop and status check spends the same rate-limit budget your publishes need — until the launch that mattered gets a 429.

Pixel-art squid invader — the 429 swarmling specimen
SPECIMEN · AS SEEN IN THE UNIVERSE
The real threat, in plain terms

QUOTAS ARE A COMMONS, AND COMMONS GET GRAZED BARE

Platform APIs give each account a budget. Naive automation treats that budget as infinite: dashboards poll, schedulers retry, health checks check — and none of it is the publish. Worse, operations that pool one set of credentials across accounts trade a quota problem for a survival problem: coordinated-behaviour detection reads shared tokens as a botnet.

  1. R1

    The graze

    Background traffic quietly consumes the window — every poll a swarmling at the till, none of them doing work a reader will ever see.

  2. R2

    The starvation

    The publish that had a timing reason — the one that mattered — arrives at an empty budget and queues, or fails, at exactly the wrong moment.

  3. R3

    The flag

    Pooled tokens make many accounts move in lockstep. To the platform that pattern has a name, and the name is not "efficient" — it's "coordinated".

The instrument built to repel it

ONE BUBBLE PER SHIP, NEVER POOLED

TOKENSHIELD — THE NET-AND-BUBBLE PLANET

TokenShield owns the token lifecycle and the budget arithmetic: one shield per account, never pooled, with launch capacity reserved before launch — Gate 03 of the chain exists so a ship discovers "no quota" on the ground, not at the dock. Housekeeping traffic is shaped to live on what's left, not the other way around.

STATUS: BEING BUILT — CAPABILITIES LANDING WITH TESTS, GAPS DOCUMENTED. SEE THE FULL MANIFEST →

THE QUOTA MECHANICS ARE FULLY DOCUMENTED — READ THE FIELD GUIDE.

PUBLISHES FIRST

Reserved, not hoped for

Launch capacity is claimed ahead of time, so the content with a timing reason never queues behind a dashboard refresh.

NO LOCKSTEP

Accounts that look like people

Per-account shields mean per-account rhythms. Nothing about your fleet's traffic pattern spells "one operator, many puppets".

GRACEFUL SCARCITY

Backpressure by design

When budget runs low, background work slows itself down — visibly, in order of importance — instead of everything failing at once.

The doctrine

The swarm cannot be fought at the moment of the 429 — by then the budget is already spent. It is fought at reservation time, which is why quota is a gate every ship threads before launch, not an error every ship discovers after.

WHY GATE 03 RESERVES INSTEAD OF RETRIES
← 01 RULE SHIFTERS03 CLAIM CRAWLERS →