Separate an HLS discontinuity from a wall-clock anchor

The useful distinctions

• DISCONTINUITY marks a boundary before the following segment.
• PROGRAM-DATE-TIME associates the next segment with an absolute time.
• These tags express different kinds of information.

Annotate two different relationships

The example places a boundary between two invented media segments and supplies an absolute time anchor for each side. The boundary says that continuity assumptions need attention; the anchors state where the segment starts map to a wall clock. The six-second difference between the anchors agrees with the first declared duration. That arithmetic consistency does not mean that the second segment continues the first segment's internal timestamp sequence.

Avoid using one field to repair another

An absolute date cannot by itself repair a missing decoding boundary, and adding a discontinuity cannot establish a wall-clock date that was never published. A useful analysis ledger records sequence identity, internal timing context, declared duration, and absolute anchor separately. When actual media becomes available, compare the track configuration and sample timestamps across the boundary. In this text-only example those values are intentionally unknown, so no claim about a required boundary trigger or successful transition is made. The worked exercise is to keep the relationships distinct and check the visible date arithmetic without inventing hidden media properties or a player's synchronization behavior. A ledger can show the media boundary and the explicit calendar anchor on separate rows. That preserves the ability to inspect a changed clock association without assuming every discontinuity represents a wall-clock jump.

Worked example · synthetic

The anchors are six seconds apart. The discontinuity is a separate declaration before after.ts; the synthetic text does not expose the actual media timestamps on either side.

Synthetic text example; no network operation has been performed.

#EXTM3U
#EXT-X-VERSION:3
#EXT-X-TARGETDURATION:6
#EXT-X-PROGRAM-DATE-TIME:2026-11-08T10:00:00Z
#EXTINF:6.0,
before.ts
#EXT-X-DISCONTINUITY
#EXT-X-PROGRAM-DATE-TIME:2026-11-08T10:00:06Z
#EXTINF:6.0,
after.ts
#EXT-X-ENDLIST

Check the interpretation

• Compare anchor arithmetic with durations.
• Check actual media changes before asserting a required trigger.
• Do not substitute date anchors for discontinuity signalling.