diff --git a/NOSTR.md b/NOSTR.md
index 7367b843d8..4212907295 100644
--- a/NOSTR.md
+++ b/NOSTR.md
@@ -156,10 +156,11 @@ out unless they ask for it:
   combine with OR, so `#t:["system", <label>]` does not mean "a system
   channel with this label".
 
-Push notifications skip system channels. Every kind:44100/44101 membership
-notification carries its channel type as `t`, and a filter without `#t` sees
-only the legacy types, so system channel notices reach only a filter with
-`#t:["system"]` (see NIP-CL).
+Push notifications use the same rule: a lease filter pushes events from a
+system channel only when its `#h` names that channel. Every kind:44100/44101
+membership notification carries its channel type as `t`, and a filter without
+`#t` sees only the legacy types, so system channel notices reach only a filter
+with `#t:["system"]` (see NIP-CL).
 
 Events are stored **channel-scoped** so access control applies — private channel member lists are
 only visible to members. Discover groups via historical REQ:
diff --git a/crates/buzz-relay/src/handlers/system_channels.rs b/crates/buzz-relay/src/handlers/system_channels.rs
index 308b87ddce..13ad914fd3 100644
--- a/crates/buzz-relay/src/handlers/system_channels.rs
+++ b/crates/buzz-relay/src/handlers/system_channels.rs
@@ -67,11 +67,6 @@ impl NamedOnlyChannels {
         &self.ids
     }
 
-    /// Whether `id` is a system channel.
-    pub(crate) fn is_system(&self, id: &Uuid) -> bool {
-        self.system.contains(id)
-    }
-
     pub(crate) fn is_empty(&self) -> bool {
         self.ids.is_empty()
     }
diff --git a/crates/buzz-relay/src/push_runtime.rs b/crates/buzz-relay/src/push_runtime.rs
index 01dd7db06a..cf6e88ab2d 100644
--- a/crates/buzz-relay/src/push_runtime.rs
+++ b/crates/buzz-relay/src/push_runtime.rs
@@ -360,8 +360,7 @@ fn match_job(
 /// REQ: a legacy-type channel is in every filter's scope (membership is
 /// checked separately), and a named-only channel is in scope only when the
 /// filter names it (see [`crate::handlers::system_channels`]). Lease filters
-/// cannot carry `#t` or `#P`, so for push "names it" means `#h`. The one
-/// exception: NIP-CL forbids push for system channels, even when named.
+/// cannot carry `#t` or `#P`, so for push "names it" means `#h`.
 fn push_filter_reads_channel(
     filter: &Filter,
     channel: Option<uuid::Uuid>,
@@ -373,9 +372,6 @@ fn push_filter_reads_channel(
     if !named_only.ids().contains(&channel) {
         return true;
     }
-    if named_only.is_system(&channel) {
-        return false;
-    }
     filter_channel_scope(filter, &[], named_only).contains(&channel)
 }
 
@@ -853,18 +849,23 @@ mod tests {
         );
         assert_eq!(wakes(&member, broad, Some(future)), 0, "unnamed later type");
 
-        // Naming a later-type channel by #h reads it, as in REQ.
+        // Naming a named-only channel by #h reads it, as in REQ: a system
+        // channel and a later-type channel alike.
         assert_eq!(
             wakes(&member, names(future), Some(future)),
             1,
             "named later type"
         );
-        // NIP-CL: a system channel never pushes, even when named.
         assert_eq!(
             wakes(&member, names(system), Some(system)),
-            0,
+            1,
             "named system"
         );
+        assert_eq!(
+            wakes(&outsider, names(system), Some(system)),
+            0,
+            "non-member system"
+        );
         // Naming one channel does not widen the filter to another.
         let other = uuid::Uuid::new_v4();
         assert_eq!(wakes(&member, names(other), Some(future)), 0, "other #h");
diff --git a/docs/nips/NIP-CL.md b/docs/nips/NIP-CL.md
index 10d395d90b..843d33f485 100644
--- a/docs/nips/NIP-CL.md
+++ b/docs/nips/NIP-CL.md
@@ -198,7 +198,11 @@ a system channel stays an ordinary NIP-29 group.
 The relay decides this for each filter. A filter that names a channel does
 not add it to another filter in the same request.
 
-The relay MUST NOT send push notifications for system channels.
+Push notifications (NIP-PL) use the same rule. A lease filter wakes its
+author for an event in a system channel or a channel of a type added later
+only when the filter names that channel. A lease filter cannot have `#t` or
+`#P`, so here "names" means `#h`. The relay still checks that the author can
+read the event, as for every other channel.
 
 ### Membership notices carry the channel type