JawnDawgs
A past NFL season, replayed.
Privileged workspace
Staff
Staff sign in with a second factor, and every action is audited. Every action on these pages is executed by the API, which is the only enforcement point: the rights gate, the editor-role gate, the separation of audit from editorial authority and, when the dormant critical-alert control is switched on, its two-distinct-editor rule are all applied server-side. Nothing here can bypass them, and a refusal is shown with the server's own reason.
Claims whose corroboration count is unadjudicated
The lineage review queue was refused by the server (HTTP 401)
Authentication required.

Sign in with a staff account to use this page.

Record a lineage judgement

Append-only: a re-review posts again and the latest recorded edge wins, so the superseded judgement stays visible. There is deliberately no edit and no delete. Naming a review task closes it with a recorded decision rather than leaving it open behind a resolved edge.

Every lineage assertion touching a Source Item

Superseded judgements are listed too. How a relationship was assessed over time is evidence, not noise, so nothing is hidden once a later review replaces it.