An 8-minute closing call: MoQT track + MLS group.
92.25 joules.

Buyer, seller, two agents, and notary each receive an INVITE per RFC 3261 §13.2.1. SDP offers OPUS@48kHz audio and AV1 video; 200 OK rolls in under 380 ms RTT. The dialog id is logged before the first packet of media moves.

Per RFC 9420 §12, an Add proposal commits and ratchets the group secret to epoch 47. The TreeKEM tree resizes from 4 to 5 leaves; previous transcript hash chains forward. Members 1–4 derive a fresh sender_data_secret before the next frame is encrypted.

Per draft-ietf-moq-transport-09, the publisher announces "closing/audio" and "closing/video" namespaces; each subscriber sends SUBSCRIBE with priority 1 (audio) and 4 (video). Object headers carry group_id + object_id so the relay can drop B-frames under congestion without breaking the stream.

AES-128-GCM exporter from the MLS epoch secret keys SRTP per RFC 3711 + RFC 8723 (double encryption). Notary's join at epoch 47 invalidates the prior key schedule — no replay of frames from epoch 46 is possible. PLI loss stays under 0.07%.

One agent dialed in from a mobile carrier — OpenSIPS 3.5 transcodes G.711 → OPUS and re-publishes onto the same MoQT track. The bridge logs an inbound CDR with PSTN charge band 12 and routes RTCP feedback back to the SFU at 250 ms intervals.

Each MoQT object is fed into a streaming BLAKE3 hasher; the final 32-byte root commits to 14,520 audio frames and 11,610 video frames. The recording artifact is content-addressed — "the audio is the evidence" means re-deriving the hash and matching is the verification.

Notary issues a Remove for itself; remaining members ratchet to epoch 48 so the post-meeting back-channel cannot be decrypted by the notary's old keys. Final epoch transcript hash is appended to the call manifest.

Recording hash, MLS epoch range [47,48], MoQT track names, SIP Call-ID, and joule total are sealed into a JWP ReceiptPayload signed Ed25519. The receipt is what downstream pillars (ComplianceOS, Veritas) treat as the closing-call evidence — no separate "recording management" system exists.