Dead as Disco Editorial Review Queue: Fact Checks, Publication Gates, and Stale Evidence
Dead as Disco 编辑审核队列：事实核查、发布门槛和过期证据
A safe review-queue framework for moving Dead as Disco sources from inbox to verified guide copy without publishing unsupported Boss, BPM, reward, unlock, or fix claims.
Evidence status
Partially verifiedThe topic and structure are reliable, but exact values or fight details still need gameplay capture.
Next: attach screenshots, timestamps, result screens, or official notes before final claims.
Use this for
Beginner Guides
Trust level
Partially verified
Reader mode
Read + verify
Editor Brief
This page is written as a working guide, not a finished wiki dump. Use the confirmed notes first, then treat source-pending rows as a checklist for what still needs gameplay proof.
Current source note: This page defines review workflow only and does not publish final Boss, BPM, reward, unlock, rank, or fix claims.
Media status
No Public Gameplay Embed Yet
This article keeps the media area honest: no fake screenshots, no decorative gameplay claims, and no third-party stills republished as site assets. When a source clip is approved, this block becomes the video player and timestamp map.
Needed
timestamped clip
Needed
claim being tested
Needed
version/platform
Queue States Before Publication
Every source should move through a review queue before it changes public guide text. The queue can use clear states: inbox, needs metadata, ready for review, verified public info, needs gameplay check, source pending, stale after update, and approved for publication. The state explains what the editor knows; it does not make the gameplay claim true by itself.
- Inbox: received but not checked.
- Needs metadata: missing timestamp, platform, version, source link, or spoiler label.
- Ready for review: complete enough for an editor to inspect.
- Approved for publication: evidence supports the exact wording that will appear on the site.
Publication Gates For Gameplay Claims
A guide should publish final gameplay claims only when the evidence matches the exact claim. A video that shows a boss attack does not automatically prove every punish window. A screenshot of a menu does not automatically prove unlock conditions. A BPM measurement does not become final without method, offset, version, and repeatability notes.
- Boss claims need move, phase/context, timestamp, platform, version, and result context.
- BPM claims need measurement method, offset/calibration note, timestamp, and repeatability note.
- Reward and unlock claims need result, inventory/menu proof, condition tested, and last checked date.
Handle Stale Evidence After Updates
Early Access pages should assume that evidence can become stale. When patch notes, store updates, or new capture disagree with an older claim, mark the affected guide as stale after update or needs recheck before rewriting advice. Old evidence should remain linked to its version so readers and editors can understand why a previous statement changed.
- Do not overwrite older evidence; retire it with version and date notes.
- Do not merge conflicting player reports into one final recommendation without review.
- Keep stale pages indexable only when they clearly show source pending or needs gameplay verification labels.
Evidence desk
Screenshot / Video Evidence Area
Editorial review states control when a source can support public guide text, but they do not validate gameplay facts without exact evidence.
This page defines review workflow only and does not publish final Boss, BPM, reward, unlock, rank, or fix claims.
FAQ
Can a review queue item become public before it is approved?
Only as a labeled framework or placeholder. It should not publish final Boss moves, BPM values, rewards, unlock paths, rank thresholds, or fixes until the exact claim has passed review.
What should editors do with conflicting sources?
Keep both sources in the queue, label the topic needs recheck, and avoid a final recommendation until platform, version, capture context, and repeatability are resolved.