Every tracked gameplay action and the packet evidence behind it. Use the work queues to find what to capture next, or search and filter the full table.
1st-person proven — a local input or request was captured together with the authoritative server result it produced. The strongest evidence.
3rd-person — the action was watched being performed by another player. That capture can never contain the other player's input, so it proves the output only.
Output only — the server output is well-attested but the local input that triggers it has not been resolved yet.
Route only — a typed client request exists on the wire with no paired authoritative result identified yet. A transport ACK does not count.
Correlated / candidate — an input classifier matches repeatedly but is not yet unique or controlled enough to call proven.
Bounded negative — scanned and absent, within a recorded scope. This means "our captures don't contain it", never "the game doesn't have it".
Not scanned — nothing has looked for evidence yet; the honest default for checklist items.
Captures column — how many distinct capture sessions contain the evidence. A capture merely declared to cover an activity is scheduling metadata, not proof.