BotScan v0.17.1 — Contest Log Analysis

1. Input and eligibility

BotScan reads selected Cabrillo logs in the protected interface and processes them through the controlled review workflow. The core parses Cabrillo headers and QSO lines, removes exact repeated QSO-line artifacts from behavioral metrics, and separates non-scored records. Standard contest review remains Single-Op; WW DIGI is the specific exception where Multi-Op logs may also be analyzed for category/compliance context, with deliberately limited bot inference.

2. Metrics

The analysis combines file integrity, rest breaks, continuous operating blocks, frequency-change rate, run/S&P texture, minute-level frequency spread, band movement, rate context, duplicate/reworked-station context and frequency-detail quality. Each metric is interpreted by mode and contest profile, not as a single global rule.

3. Peer comparison

Each established contest and category has its own historical peer profile. BotScan compares the uploaded log against matching Single-Op groups by contest, year, mode, power, band and assistance where available. WW DIGI is handled separately with category-aware rules and published historical rate references while its full public-log baseline is being expanded, so digital operation is not forced through CW/RTTY/SSB frequency-movement rules.

4. Evidence logic

BotScan avoids relying on one weak signal. RED-level review requires hard timing, scanner/no-run structure, hard minute-level spread, or multiple independent evidence families. In RTTY Single-Op review, 5+ distinct logged frequencies in one minute remains a high-priority hard spread signal. Frequency-spread display now starts at 4+ and dynamically reveals higher 7+/8+ levels only when they are present. Three-frequency minutes are retained only as internal/informational context. In CW, isolated single-band 5-frequency minutes are treated as aggressive S&P context; repeated 5+ or any 6+ minute remains high-priority review. In SSB, stable dual-run/2BSIQ and aggressive S&P are handled separately, and SSB scatter is compared against the matching historical peer-group peer reference/max before it affects review level. Fast duplicates and same-band reworked stations remain context only and do not create RED by themselves. For WW DIGI, legal SO2R/2BSIQ is explicitly protected: SINGLE-ONE and MULTI-ONE are limited by transmitted signals, not by radios in use. Exactly two bands inside one Cabrillo minute is normal operating context; repeated 3+ band minutes are rare screening texture, never proof of simultaneous TX.

5. Batch ranking context

In batch mode, claimed score is used only to show pre-adjudication rank inside the loaded category group. Automation Evidence is calculated separately from claimed rank.

6. Limitations

Cabrillo timestamps are usually minute-level, so the tool is a screening layer. This limitation is especially important in WW DIGI: logged frequency is treated as dial/subband information, not as the individual FT4/FT8 audio DF/offset. Cabrillo cannot reveal the operator action that initiated a QSO, exact TX-slot overlap, decode-source provenance or receiver location. Historical rate statistics are outlier context, not proof thresholds. Strong WW DIGI flags should be followed with the original ADIF, complete native RX/TX/decode logs from every software instance, and FT4/FT8 RBN correlation where available.

7. Historical Results Audit

The historical audit includes RED-only Single-Op cases and cross-references them with official CQ and ARRL final results. BotScan evidence, official rank, disqualification status and record references remain separate data layers. A RED row is not, by itself, proof of autonomous operation or a rules violation.