Server roadmap¶
This is the separate rfSentry Server roadmap; its phase numbers do not refer
to the WebSDR delivery sequence. On 2026-11-09, the operator accepted
Server Phase 8 and only the authorized Phase 9 Server-product consumption
at 744b840a5c9b3c15967d84d45e777b686779c8da, originally released as v0.6.19-phase8-q2 (since retired).
Main qualification
and release qualification
succeeded, including both installed architectures in the release. These results
bind that source; this documentation close-out is not a new package qualification.
- [x] ~~Server Phase 8: optional product reconstruction and delivery.~~ Generic compiled processor contracts, supervised admission, durable products/recovery, item-failure continuation and live/newest-first history processing are accepted. GOES/HRIT is the production adapter: supported native imagery, text/messages, environmental products, originals, thumbnails, Natural Color and Day/Night. Generic contracts and test processors do not implement other production decoders.
- [x] ~~Narrow Server Phase 9: consume Server-produced products in the browser.~~ Bounded discovery/transfer, durable OPFS/IndexedDB import, independent retention and existing viewers are accepted. Product mode suppresses corresponding local assembly/recipes; direct IQ, appliance records and archive-only Servers remain.
| Server phase | Status and retained boundary |
|---|---|
| 1 — Assessment/design | Accepted for progression, not blanket approval of defaults. |
| 2 — Shared C++/WASM64 foundation | Accepted; >4-GiB execution remains unqualified. |
| 3 — Continuous appliance SATCOM decoding | Accepted, including its focused corrections and CPU follow-ups. |
| 4 — Protected Pi RAM and resumable records | Accepted, including quota and empty-snapshot corrections; no appliance payload persistence. |
| 5 — Server package/admin/onboarding | Accepted, including full-access pairing and optional authentication. |
| 6 — Durable record ingestion/archive | Implemented and correctness-qualified; operator performance acceptance remains separate and open. |
| 7 — Browser records/direct-appliance fallback | Operator-accepted 2026-10-31. |
| 8 — Optional Server reconstruction | Operator-accepted 2026-11-09 at the baseline above. |
| 9 — Product synchronization/caching | Only the narrow consumption scope above is accepted. Remaining scope needs a separate proposal/authorization, preserving fidelity, offline/cancel/resume and source-transition guarantees. |
| 10 — Multiple-server registration/selective replication | Future authorization: directed trust/filter policy, independent positions/retention, original identities, loop/conflict prevention and no master dependency. |
| 11 — Peer relay/on-demand hydration | Future authorization: retention-optional live relay, scoped missing-range/product hydration, bounded cancellation, cycle/unreachable-peer handling and no false durable ACK or arbitrary proxy. |
| 12 — Integrated reliability/release qualification | Future authorization: combined zero/one/multi-server, multi-stream, security/resource/upgrade, supported browser/platform and live/fault/soak evidence. Existing releases do not close this integrated gate. |
Independent open follow-ups remain #5 hidden-main-document radar preparation, #6 Full Disk cold-loading, and #7 mount-table incident/recovery (the last remains deferred unless it recurs). None is closed by acceptance. The validation chapter retains the historical sanitizer watchdog uncertainty and unmeasured resource, platform and durability limits separately from functional acceptance.
Operating contracts live in Server operations, browser sources, storage architecture, ARCHIVE.md and PRODUCTS.md.
Dependencies and verification¶
Verification index retains bounded source-specific records for delivery, onboarding, archive regression and browser reconstruction. Historical release/commit identifiers describe the observed source; removed tags and rewritten history may no longer resolve. They do not qualify current source.
Keep available, durable and browser-recoverable positions independent. Storage ACKs require segment/index durability; processing never owns acquisition ACKs. Retention-aware history prioritizes newest missing intervals with forward reconstruction and explicit gaps. Admission reservations survive until reaping; resource policy must protect ingestion/control headroom.
The 2026-10-28 compatibility decision permits pinned MEMORY64=2 only when native MEMORY64=1 is unavailable, with the same wasm64 layout/i64 ABI and exclusive OPFS ownership. This does not prove >4-GiB execution. The 2026-10-29 resource policy preserves native pixels/history and explicit workstation settings; iPad/device recovery and rendering still need their own evidence.