Epic: Psychological horror identity layer for Case Box 001

[breadback00-dev]

Summary

Add the first psychological-horror slice to Case Box 001: unreliable evidence, consent-cost decisions, a player-action trace, consequence/debrief surfaces, and subtle sensory corruption.

This work should preserve the existing static investigation loop: stable canonical truth, route responsiveness, reconstruction board, gate, and custody choices.

Plan

Local plan artifact:

online game concept/docs/plans/2026-05-24-002-feature-psychological-horror-layer-plan.md

Requirements

• The interface gradually escalates from neutral archive to unreliable mirror based on in-case actions.
• At least two artifacts can shift, echo, or expose alternate versions without changing canonical truth.
• Consent-cost choices produce visible consequences in framing, entity reactions, debrief, or custody tone.
• The player’s own actions appear in a visible Archive Trace / Timeline of Self.
• Horror style uses dread, uncertainty, implication, subtle corruption, and optional micro-audio rather than jump scares or graphic content.
• Final debrief reflects identity treatment: preservation, appropriation, or dissolution.
• Personalization remains session-local and action-style based; no real identity, device data, external tracking, accounts, analytics, or backend persistence.
• Safety controls reduce motion/corruption, mute audio, and keep case-critical evidence accessible.

Child issues

• U1: Define horror content model and safety copy #17
• U2: Add horror state, action trace, and tests #18
• U3: Implement unreliable evidence and echoes #19
• U4: Add consent-cost choices and consequences #20
• U5: Build Archive Trace, living dossier reactions, and debrief #21
• U6: Add sensory corruption, micro-audio, and intensity controls #22
• U7: Update docs, public copy, and verification #23

Completion criteria

• Core Case Box path still works for first-time investigation.
• Unreliable evidence, consent pressure, action trace, debrief, and sensory controls are implemented.
• Static checks, pure helper tests, and desktop/mobile browser playthroughs pass.