One session holding many concurrent virtual-queue positions — a position-hoarding scalper
bh.arena_queue_hoarding · convicts
What it catches
Kitsune arena challenge-solve coherence (waiting-room / virtual-queue gate): a scalper maximises its odds in a rate-limited waiting-room by HOARDING many concurrent positions. The detector counts a session's (ks_sid) outstanding queue tickets SERVER-SIDE (minted at GET /arena/queue, dropped at POST /arena/queue/act, pruned by a 2-minute TTL so abandoned positions do not accumulate); more than 8 concurrent is a position-hoarder, not a person — even a multi-tab human does not hold 9+ queue positions at once. On threshold-crossing the detector injects behavioral.arena_queue_hoarding on ks_sid. EXPERIMENTAL / corroborating (w0.5, cannot convict alone): unlike the by-construction admission-timing tells (bh.arena_queue_superhuman / bh.arena_queue_bypass), the hoarding threshold is CALIBRATED, so a rare heavy-multi-tab human is not framed on this alone. The per-ORIGIN form is in-sandbox-confounded (all lab traffic shares the detector egress), so this is keyed per-ks_sid — which catches the NAIVE hoarder reusing one session; the SMART hoarder spreads positions across distinct ks_sids/fingerprints, which is the sybil-farmer coordination frontier (external-data-bound, mapped closed on the coordination axis). GROUNDED LIVE 2026-07-03: a session that mints 9 concurrent tickets trips the signal + rule; a session cycling one ticket at a time (mint->act->mint) never does. See docs/research-radar.md (arena waiting-room loop).
Signals it reads
behavioral.arena_queue_hoarding
How it fires
present
Bypassed by 10
Frontier evaders that reach the detector uncaught (scored only suspicious, defeating every convicting tell) — this check is not one that stops them. The red-team frontier this detection still has to convict.