Liverpool v Arsenal

Absent, with the reason

These are absent rather than shown empty, and each says what it is waiting for.

• Match Story™

  What happened in this match, in order, with every sentence citing its events.

  What it does not answer. It never says who played well, who was at fault or what the match meant. A sentence here is a rendering of a recorded event and nothing else; where the platform holds no event, the story has no sentence rather than a general one.

  Basis: The recorded event timeline for this match, ordered by canonical sequence.

  Not available at this coverage — No event timeline is admitted for this match, and this product is a function of one.

• Drama Meter™

  How eventful the match already was — swing events, lead changes and whether a goal late in the match changed who was ahead.

  What it does not answer. It is not a recommendation and not a prediction. It never orders one match above another, never suggests what to watch, and is computed only after the events it counts have happened.

  Basis: The nine canonical swing event types, counted from this match’s own timeline.

  Not available at this coverage — No event timeline is admitted for this match, and this product is a function of one.

• Match Pulse™

  When the match was busiest, phase by phase, against its own average.

  What it does not answer. It is not a comparison with any other match. The scale is this match’s own mean, so a quiet match reads as quiet instead of being stretched to look eventful.

  Basis: Every recorded event, grouped into six phases of the clock.

  Not available at this coverage — No event timeline is admitted for this match, and this product is a function of one.

• Match DNA™

  The shape of the match across five governed constructs, each with its definition version and the events that produced it.

  What it does not answer. There is no overall figure. The profile is the product: reducing five constructs to one number would be the composite the football specification refuses. Where a construct cannot be grounded it is absent with its reason, never shown weakly.

  Basis: The construct registry, applied to this match’s recorded events.

  Not available at this coverage — No construct in the profile can be grounded in what the platform holds for this match. Each is listed below with the reason, which is the answer to the question the category never asks: what do we not know, and why.