From 5c0b6402ed0b0f52f79673a174d01a878e060f96 Mon Sep 17 00:00:00 2001 From: archipelago Date: Tue, 6 Oct 2026 02:00:56 -0400 Subject: [PATCH] Require standard MeshCore public channels and defer custom channels --- docs/post-1.9.0-work-backlog.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/docs/post-1.9.0-work-backlog.md b/docs/post-1.9.0-work-backlog.md index 78f6a92a..083b935b 100644 --- a/docs/post-1.9.0-work-backlog.md +++ b/docs/post-1.9.0-work-backlog.md @@ -350,3 +350,13 @@ investigation for this scoped task; earlier hardware deferral is not a pass. listener stability, restart/reconnect and meaningful negative cases. Record firmware/builds, radios, conditions and results. Simulated or headless checks alone do not constitute RF acceptance or a claim of flawless operation. + +### MeshCore channel scope clarification + +The operator explicitly requires the standard MeshCore public channel(s) used +by the wider community, not an Archipelago-specific/custom channel. Verify the +current official default channel identity/key/configuration and interoperability +with standard MeshCore clients on the selected UK RF plan. Two Archipelago radios +agreeing with each other on a private/custom channel is not acceptance. Custom +channel creation/configuration is deferred to later work and must not be added +as a substitute for repairing the standard public-channel experience.