Clients and trust roadmap¶
Status: the unified workstation utility and appliance-owned private PKI are implemented. Platform onboarding, offline mobile installation and broad device acceptance require their own evidence; publication approval is not acceptance. WebSDR Phase 5 remains deferred. Native local-client work is a proposal only.
Scope and decisions¶
The 2026-10-24 operator decision unifies normal and diagnostic setup in one
rfsentry-client binary per OS/architecture. Keep separate settings, ownership
markers, browser profiles and shortcuts. Browser support is explicit, loopback
only and never a persistent service. Strict HTTPS, normal browser sandbox and
conservative launch modes remain mandatory. macOS application/login identity
comes from user configuration or preserved installed metadata, never a personal
namespace in source. See workstation setup.
One root per appliance trust domain, a constrained issuer and persistent Server enrollment keys support offline renewal without a project-wide master secret. Root replacement requires retrust; issuer rotation under that root does not. The trust ADR owns the reasoning and identity guide the procedure.
Dependencies and acceptance criteria¶
Preserve transactional PKI publication, exact name approval, no private keys in APIs/logs/packages, and explicit recovery for lost/revoked keys or expanded names. Verify root/intermediate/leaf constraints, CSR sanitization, suffix/CIDR policy, replay/lost-response recovery, expiry, clock error, rotation and revocation. The onboarding record separates local checks from installed lifecycle results and unresolved helper behavior.
Mobile acceptance must exercise Android and iOS trust, fingerprint comparison, PWA setup, multiple paired Servers and offline shortcuts. Chrome WebAPK minting can require an online service; private PKI alone does not prove fully offline app-drawer installation. A separately signed wrapper requires a later decision.
Phase 5 โ Simplified Mobile Experience¶
Deferred by the operator on 2026-08-27. This phase remains open. Its automatic-scan interactions remain coupled to the deferred Phase 4 work. No checklist item below is completed or removed by the deferral.
- [ ] Implement the mobile
Listen,Scan,Signals, andControlsviews. - [ ] Make scan-plan selection, scan speed, start/pause/stop, detection holds, detected-signal selection, and detection actions fully usable by touch.
- [ ] Implement direct entry, fine/coarse stepping, swipe tuning, pinch zoom, filter adjustment, mode selection, and essential receiver/audio controls.
- [ ] Implement complete signal-information and decoder-result sheets.
- [ ] Expose a touch-friendly intelligent-activation action in the signal sheet using the same command, progress, pin, cancel, and undo contracts as desktop double-click.
- [ ] Add adaptive Eco/Balanced behavior for phone CPU, memory, network, and battery constraints.
- [ ] Handle rotation, foreground interruption, browser suspension, reconnect, and loss of receiver control explicitly.
- [ ] Validate accessibility, touch targets, portrait/landscape layout, audio stability, and representative phones/tablets.
- [ ] Validate Phase 5 deliverables and update the completion ledger.
Native client proposal¶
See native local client evaluation. Its staged feasibility, coexistence and prototype gates do not authorize replacement of the browser.