First public, citable release of the Radio Communication Subtopology for F′ (F Prime) — an open-source structural scaffolding that wires a custom radio link protocol into the standard F′ communications services, so flight-software teams can drop in their own framing logic without rebuilding the topology. This release captures the project as used by the Utah State University Get Away Special (GAS) Student Satellite Team and establishes a stable, taggable reference point for citation and reuse. What's included Reusable FPP subtopology — RadioProtocol A self-contained F′ subtopology that connects custom framing components to standard F′ services (Svc.ComQueue, Svc.FrameAccumulator, Svc.FprimeRouter, Svc.BufferManager, Svc.ComStub) across fully-defined uplink and downlink paths. Drop it into any deployment with a single import RadioProtocol.Subtopology. Queue depths, priorities, stack sizes, and buffer-manager bins are centralized in RadioProtocolConfig. Link-protocol components — LinkProtocols/RadioLinkProtocol RadioFramer — wraps outgoing F′ packets into radio/link frames. RadioDeframer — strips link headers from incoming frames and routes packets to the FprimeRouter. RadioFrameDetector — an Svc::FrameDetector implementation that locates frame boundaries in a continuous byte stream for the FrameAccumulator. CRC16 helper for frame-check computation. The framing bodies are intentionally stubbed as pass-throughs. The repository ships the structure; operators supply the algorithm-specific details (preamble, sync word, length field, CRC polynomial) against their own radio's datasheet. This keeps the scaffolding generic and keeps vendor-/IP-specific values out of the public tree. Management components — Components/ TransceiverCommsManager — active downlink gateway and beacon state machine spanning five states (SILENT → ACTIVE_BEACON ↔ LOW_POWER ↔ DOWNLINKING ↔ DISABLED), including a 30-minute LEOP silent period, periodic and low-power beacon cadences, downlink-pause logic, and health-ping support. Covered by 9 passing unit tests. TransceiverConfigurationManager — active component that configures the transceiver over I2C (frequency, callsigns, power mode) with per-transaction status events. Configuration injection layer — keys_template/ A single-header injection mechanism (TransceiverConfig.hpp.example) for supplying radio-specific constants — preamble, sync word, CRC polynomial/init, I2C address and command strings, and beacon payload — at build time. The populated header is git-ignored, keeping mission- and vendor-specific values out of the public repository. Example deployment — Deployments/RadioDeployment A complete, buildable F′ deployment that demonstrates the stack integrated alongside the standard F′ core subtopologies (CdhCore, ComCcsds, FileHandling, DataProducts), with a Raspberry Pi cross-compilation and GDS-over-TCP hardware setup guide. Documentation docs/ARCHITECTURE.md — architectural specification. docs/USAGE_GUIDE.md — step-by-step integration guide. docs/IMPLEMENTATION.MD — scaffolding vs. injected-logic breakdown. Per-component software design documents (SDDs) and a hardware setup guide. Requirements F′ (F Prime) framework, version > v4 (included as a git submodule). A C++11/17 toolchain and FPP. Status & scope This is a structural reference / integration template, not a turn-key radio driver. The management logic, topology wiring, configuration plumbing, and example deployment are complete and exercised by unit tests; the link-layer framing algorithm is intentionally left as marked stubs for the integrating team to implement. See docs/USAGE_GUIDE.md to get started. License Released under the MIT License. Copyright © 2026 Utah State University Get Away Special Student Satellite Team.