KILL LOG EVIDENCE-FIRST RETRACTION
Rumors the desk has killed.
Each entry names the original source the rumor came from, the evidence that retired it, and the UTC timestamp the claim moved to killed status. Gaming press operates on velocity incentives that make a public retraction list structurally hard to maintain. The desk does.
0
No kills on the books yet.
A kill needs a claim that was on the register and a source-chain entry that retires it. The first one lands here the moment the chain produces it. Until then, the desk publishes the path each transition takes.
How this list gets populated
01 Tier 1 contradiction
A tier-3 community claim on the register picks up a direct tier-1 contradiction. The kill source is the contradicting first-party post; the kill date is the post's publication timestamp. Example trigger: a leak-cohort X post claiming a specific feature, followed by a Rockstar Newswire post that names the same feature and contradicts it.
02 Kill-conditions timeout
A watching-verdict row carries an explicit kill_conditions clause with a fixed timeout (typical: ninety days from row open) and no higher-tier source surfaces inside the window. The operator moves the row to killed on the next review cycle. The kill source is the desk transition; the kill date is the timeout expiry, not the review timestamp.
03 Take-Two SEC filing
A tier-2 amplified rumor is contradicted by a specific line in a Take-Two 10-Q, 10-K, or 8-K filing. The kill source is the EDGAR filing URL pinned to the exact section reference; the kill date is the filing acceptance timestamp on EDGAR, not the press amplification date.