diff --git a/crates/rutster-media/src/rtc_session.rs b/crates/rutster-media/src/rtc_session.rs
index b490c9d..a4c9f2a 100644
--- a/crates/rutster-media/src/rtc_session.rs
+++ b/crates/rutster-media/src/rtc_session.rs
@@ -10,11 +10,12 @@
 //! str0m 0.21's `Rtc::sdp_api().accept_offer(offer)` produces the SDP
 //! answer natively: DTLS fingerprint (from the cert str0m generates), ICE
 //! ufrag/pwd, and codec negotiation (Opus, the only codec we registered).
-//! Slice 1 does NOT hand-roll an SDP munger — str0m's path is the spec's
-//! "embryo of the future SIP SDP path" (§3.7). When step 5 brings SIP/SDP
-//! negotiation into `rutster-signaling-sip`, that crate may extract shared
-//! SDP helpers from str0m or build its own. Slice 1's WebRTC-ICE-coupled
-//! SDP lives entirely in str0m.
+//! Slice 1 does NOT hand-roll an SDP munger — str0m handles WebRTC
+//! offer/answer natively. There is no first-party SIP/SDP path: under
+//! [ADR-0007](../../../docs/adr/0007-trunk-rented-transport.md) the trunk is
+//! rented (a CPaaS media-leg fork — raw audio, no SDP) or an out-of-tree SBC
+//! (which owns any carrier SIP/SDP, outside the trust boundary). rutster's
+//! WebRTC-ICE-coupled SDP lives entirely in str0m.
 
 use std::net::SocketAddr;
 use std::time::{Duration, Instant};