Dead as Disco Corrections Log Policy: Change History, Evidence Updates, and Rechecks
Dead as Disco 更正记录政策：变更历史、证据更新和复核
A safe corrections-log framework for Dead as Disco guide updates, covering public correction notes, stale claim replacement, evidence update records, and reviewer audit trails without publishing unverified gameplay changes.
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 correction workflow only and does not publish exact changed gameplay facts.
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
Corrections Need A Source Trail
A correction log should explain why public guide copy changed, but it should not publish a new gameplay claim until the evidence is reviewed. Each correction should record the affected page, old claim status, new evidence type, reviewer note, version or date, and whether the public copy changed, stayed source pending, or moved back to needs gameplay verification.
- Record the affected page and exact section, not just a general topic.
- Link the correction to evidence metadata, not an unsupported player memory.
- Use source pending when the correction is suspected but not verified.
- Keep old evidence attached to its version so the change can be audited later.
What Public Change Notes Should Say
Public notes should be short, factual, and scoped to editorial status. They can say that a page was refreshed after new evidence, that a claim was moved back to review, or that a placeholder was replaced with verified wording. They should not reveal unverified Boss moves, BPM changes, reward changes, unlock paths, hidden achievements, fixes, or endings.
- Safe: updated evidence status after new capture review.
- Safe: moved a claim from partially verified to needs gameplay verification.
- Unsafe: publishing the exact new value before evidence review is complete.
- Unsafe: using correction notes to bypass spoiler labels.
Stale Claim Replacement Workflow
When a patch, store update, new screenshot, or new video conflicts with older guide copy, editors should mark the old claim stale before replacing it. Replacement copy should match the exact evidence and carry its version, capture date, and reviewer note. If the evidence only proves that the old claim is uncertain, the page should say needs recheck instead of inventing a new answer.
- Mark stale first, then review evidence, then update public copy.
- Do not collapse conflicting sources into a single final answer without reviewer notes.
- Keep corrections visible enough for reader trust but spoiler-safe in public listings.
Evidence desk
Screenshot / Video Evidence Area
Public corrections should record affected pages, evidence metadata, reviewer notes, old status, new status, and last checked date before changing final guide copy.
This page defines correction workflow only and does not publish exact changed gameplay facts.
FAQ
Does this page list real Dead as Disco corrections?
No. It defines the corrections-log workflow only. Real correction entries should be added only after evidence metadata and reviewer notes exist.
Can a correction note publish exact changed gameplay values?
Only after evidence review is complete and the article has the correct spoiler placement. Until then, use source pending, needs recheck, or needs gameplay verification.