Hunting Ground Management

Correction note — verbatim, with source locators

Confirmed tier-scoped payload_cross_contamination (Lot 9 gate report §2.1/§3.2): Tier 1 (Mikro/Kecil/Menengah/Besar scale) is verbatim byte-identical to 93191's own correct tier, naming 'Promotor Kegiatan Olahraga' (sports-event promoter activity) — an activity 93193 has nothing to do with. Tier 2 (Kecil/Menengah/Besar scale) correctly names 93193's own activity ('Aktivitas Perburuan', hunting activities) but has NO PP28 row anywhere in the 21-file/11,208-page vault (pp28/ABSENT.json) and no OSS endpoints either — 93193 has ZERO genuinely sound tiers (Lot 9 gate report §2.1, Kimi K3 red-team F2 correction). Lot 9 held per_skala completely untouched (action: metadata_only, only a status_mapping/whatChanged correction applied) pending a per-tier selector that now exists (PR #2921, 2026-07-21) — but unlike 93191 (which keeps one genuinely-sound tier via partial_detach in this same spec), 93193 has nothing left to preserve once the contaminated Tier 1 is removed, since its own Tier 2 is independently unconfirmable against any PP28/OSS source (Lot 9 gate report explicitly predicted this: 'the likely end-state once it lands is full detach (both tiers unconfirmable), not a partial cure'). Cure: plain full detach (default action, no per-tier selector needed) — both tiers moved verbatim to the disputed key, per_skala -> []. status_mapping (MATCH_CON_AGGREGAZIONE) and intel_2026.whatChanged were already corrected at Lot 9 and are NOT touched again by this entry.