The Hunt is a 14-part deep dive into the part of GopherTrunk that finds systems you didn’t know were there. Where the Trunking Engine series started from a known control channel and turned its grants into calls, this series starts one step earlier — from a blank band — and works forward: sweep the spectrum, pull carriers out of the noise, classify what each one is, lock a control channel, reconstruct a system’s channel map and its sites, harvest the aliases riding on its traffic, and export the whole find so someone else can tune it in seconds.

It is the detective arc. Where Signal Lab taught you to name the unknown from a single capture on a workbench, The Hunt does it live and at band scale — the same measurements, driving a search. One thread runs the length of the series: a stray carrier that shows up in a routine survey, and everything it takes to turn it into a named, mapped, exportable system.

Every post reads three ways: a TL;DR + cheat-sheet for skimmers, bold headers, tables, and diagrams for the medium read, and full prose with real code for the deep read.

New here? Start with the Digital Trunking module for how a trunked system is laid out, then come back for how GopherTrunk finds one.<ol class="post-list series-list"><li class="post-card"> <h2 class="post-card__title">The Hunt, Part 1: What Discovery Means — From a Blank Band to a Known System</h2> <p class="post-card__meta"> August 4, 2026 Deep dives </p><p class="post-card__desc">How GopherTrunk turns an empty stretch of spectrum into a named, mapped trunked system — the sweep, identify, and map pipeline behind the hunt engine, and the one discovery contract that the CLI, the daemon, and the web cockpit all drive.</p></li></ol><p class="blog-feed-link"> See all deep dives or subscribe via RSS. </p>