Skip to content

ADR 0004: Explicit receiver paths and foreground scan ownership

  • Status: accepted
  • Date: 2026-08-24

Decision

RF frequency and tuner frequency are distinct values. A receiver-path profile contains ordered translation/filter stages, supported tuner/RF ranges, verification state, and this convention:

rf_hz = tuner_hz - net_translation_hz

Unknown offsets remain null; they are never guessed. Such paths cannot be enabled for automatic scanning. Profiles are selected explicitly per receiver.

Automatic scanning is foreground and browser-owned in the initial product: an active, visible client holds the receiver lease and advances a versioned scan plan. Disconnect cancels the plan and releases the upstream stream. Scan plans express ranges, exclusions, step/overlap, settle/dwell, detection thresholds, hold/stop policy, and actions. Results retain both RF and tuner coordinates plus the exact path-profile revision.

Consequences

The current Ham It Up path is intentionally unverified in Phase 0. Calibration is an operator-visible task, not a hard-coded assumption. Persistent unattended server scanning is a possible later architecture change requiring a phase gate and explicit power policy.