1. The lamp stayed on.
Deadpan Packet inspects a lit lamp with one cord running from its base to a wall outlet. A separate before-and-after line preserves the continuity of the light; this is a metaphor for the reported ingest migration, not a network schematic.
iOS / Android ingest; delivery all the way to viewers remains future work.
Source: https://blog.rvnd.me/moqmusings/2026-10-12-moq-kept-the-lights-on#instagram-ingest

2. Check the actual version.
Two deadpan Packet characters compare differently shaped blank badges at a coat-check counter. Separate labels compare client reports with the test report and identify 18 differences among 76 version reports.
The records disagree about the version used. They do not count failed streams.
Source: https://blog.rvnd.me/moqmusings/2026-10-12-moq-kept-the-lights-on#seattle-interop

3. Permission has a clock.
A deadpan Packet holds an hourglass and a small stop gesture beside an old admission ticket and a rope entrance. The separately typeset instruction to renew before expiry illustrates the proposed lifetime permission checks.
Proposed relay-to-client checks: renew permission or stop delivery.
Source: https://blog.rvnd.me/moqmusings/2026-10-12-moq-kept-the-lights-on#authorization-renewal

4. Put publishers under the lens.
A deadpan Packet examines a printed report with a magnifying glass. One separate cable visibly connects the camera to the recorder, which emits a dotted strip. Separate publisher-to-evidence-to-report labels explain wire-level testing rather than validation of the pictured media.
Existing tool. Drafts 18/21/22; separate moq-lite-06. Trusted-network API; no media checks.
Source: https://blog.rvnd.me/moqmusings/2026-10-12-moq-kept-the-lights-on#built-with-moq
