05The hard parts
Events are not possession
Events and tags are sparse moments. Possession is a state on every frame, including all the frames between them. What a touch, a header or a tagged phase is allowed to change, and how much it should weigh.
- Events
- Tactical tags
- Sparse to dense
- Fielded
- Events
- Sparse: pass, header, tackle, out, restart
- Possession
- Dense: one state on every frame
- Design choice
- Hard boundary, transition cue, or weighted evidence
- Timing gap
- One second is 25 frames at 25 fps
The design question
How should a sparse signal inform a dense one? Event spotting produces moments. Possession inference owes a state to every frame. The design has to say what an event is allowed to change. What the supplied tags are is described in Tags are context, not events.
What each signal proves
| Signal | Proves | Cannot prove |
|---|---|---|
| A detected touch | Contact near this instant | That control changed hands |
| A header or tackle | A contest took place | Who came out with the ball |
| Ball out, restart | A stoppage boundary nearby | Its exact first and last frame |
| A tactical phase tag | The shape of play around now | Which frame it began |
| A set-piece tag | A restart is coming | How long the ball was dead |
Three ways to use them
| Use | How | Costs |
|---|---|---|
| Hard boundaries | Cut the sequence at each event | Every false event splits a possession |
| Transition cues | Lower the decoder’s switch cost near an event | Needs a timing window |
| Weighted evidence | Add a small score for the implied state | Weights must be earned, not guessed |
Whichever is used, a tag that names a team is evidence about the team only. Why it must stay out of the alive-or-dead question is the subject of Alive or dead, then who.
Tags name a team, not an owner
A phase tag that names a team does not say that team has the ball. “Build up” names the side in possession. A defending phase names the side without it. The safe design measures what each code means against something observable before giving it a vote.
What breaks it in real football
- A headed clearance to nobody. The contest is real and the next controlled touch is seconds away.
- Overlapping phases. Transition and build-up are tagged at once, for opposite teams.
How to judge it
Measure boundary error in frames, never in seconds. Count how many events changed the decoded possession and how many of those changes were right. Then switch the event evidence off: if both official metrics hold, the events were decoration.
Our read
Use events to propose boundaries and let control evidence confirm them. A spotter accurate to a second cannot place a turnover to the frame.
Our call
ConstraintData reality and competition rules
Why the tags calibrate themselves
The tags are automatic, and the team a code names is the side on the ball for some codes and the side off it for others. With no answers to tune on, the pipeline measures how often each code's team agrees with visible ball control and turns that into a weight. Build up lands at +1.86, its defending mirror at -1.86, and tags stay a light hint beside ball control.