diff --git a/docs/ROADMAP.md b/docs/ROADMAP.md
index b1a6398..303676d 100644
--- a/docs/ROADMAP.md
+++ b/docs/ROADMAP.md
@@ -618,18 +618,24 @@ Deferred deliberately, in rough priority order:
 - **Migrate Calendula and Agendula onto `core-prefs` + `core-di`**: tracked in
   the kit's roadmap, not here.
 - **Wear OS companion** ([#27](https://codeberg.org/jlmakiola/clockula/issues/27)):
-  unscoped, and blocked on one constraint. A companion that shows and controls
-  the phone's timers and next alarm needs a phone-to-watch channel, and the only
-  practical one is Google Play Services' Wearable Data Layer
-  (`play-services-wearable`). That is a proprietary third-party service, so it
-  would break `PRIVACY.md`'s "no third-party service of any kind" and the
-  F-Droid build. What already works without it: ring, timer and snooze
-  notifications are bridged to a paired watch by the system, so the wrist
-  already gets the ring and its actions. The options, if this is ever picked up:
+  unscoped. The part the issue describes, a watch that shows and controls the
+  phone's timers and next alarm, needs a phone-to-watch channel. The usual one
+  is Google Play Services' Wearable Data Layer (`play-services-wearable`), a
+  proprietary service that `docs/PRIVACY.md` ("no analytics, tracking,
+  advertising, crash-reporting SDK or third-party service of any kind") and the
+  F-Droid build rule out. Other channels (a Bluetooth link of our own through
+  `CompanionDeviceManager`) haven't been looked into.
+  Today a watch gets little: ring and timer notifications are ongoing, which
+  Wear OS doesn't bridge by default, and bridging itself goes through Google's
+  Wear OS app on the phone, so a degoogled phone gets none of it. Only the
+  "Snoozed until" notification reaches a watch on a Google phone. The options,
+  if this is picked up:
   - **Standalone watch app**: its own timers, stopwatch and alarms on the watch,
-    no Play Services and no sync. Fits the privacy promise but does not control
-    the phone.
+    no Play Services and no sync. Not blocked by anything; it just doesn't
+    control the phone.
   - **Play-only companion**: the Data Layer confined to a Play Store flavour, so
     F-Droid builds stay free. It means two flavours with different features and
     a privacy policy that has to describe the difference.
-  - **Leave it**: rely on the bridged notifications and do nothing more.
+  - **Bridge the ring**: let the ring and timer notifications reach a watch
+    (not ongoing, or a separate bridged notification), keeping in mind that a
+    dismiss challenge makes Dismiss open the phone's ring screen.