1. Mind the missing object.
Packet kneels by a tray and inspects an empty compartment with a magnifying glass. Separate labels distinguish sent objects from received objects.
Caches must distinguish missing, filtered and deliberately absent data. The working group has not adopted a new numbering rule.
Source: https://blog.rvnd.me/moqmusings/2026-10-19-moq-minded-the-gap#object-numbers

2. An early finish flag.
Packet stands holding a finish flag beside a lowered gate that separates two cargo blocks on a conveyor. The flag is premature because one block is held back.
An updated filter can exclude the final object. What should closing the stream tell the receiver?
Source: https://blog.rvnd.me/moqmusings/2026-10-19-moq-minded-the-gap#finish-flag

3. Bring a worked example.
One Packet holds an empty display plinth while another waits with a pencil. The illustration represents an unprovided worked example, not a completed implementation.
Editors want an example extension before San Francisco. Removal is a conditional proposal, not a decision.
Source: https://blog.rvnd.me/moqmusings/2026-10-19-moq-minded-the-gap#mandatory-properties

4. One game. Several drivers.
Two deadpan Packets hold wireless controllers beside one supported monitor showing abstract pixel blocks. Their different postures suggest disagreement over the controls.
Controls and game status travel on JSON tracks. No gameplay benchmark or universal interoperability claim.
Source: https://blog.rvnd.me/moqmusings/2026-10-19-moq-minded-the-gap#built-with-moq
