A first-run route from house baseline to visitor check, porch-light response, and post-knock review.
Find the laptop and its normal/night-vision toggle, the parents' bedroom, kitchen oven and sink, bathroom faucet, backyard view, car view, front door, and porch-light switch. This turns later claims into location checks instead of memory tests.
A room claim belongs to house state; a shape change belongs to normal-versus-night vision; a voice change belongs to audio; a car, dog, or yard claim belongs to outside views. Open the systems map when the channel is not obvious.
Horror atmosphere, uniforms, and unfamiliar animations are not enough. Match the reported car, cat colour, faucet state, voice change, size change, prop, expression, or movement.
Record the visitor, channel, exact observation, platform, and date. A conflict is a useful Needs another check result, not a reason to invent a rule.
Tour the key rooms and camera feeds before a visitor makes a claim about them.
Use the visitor table; roster-only names deliberately do not have thin detail pages.
Keep the same camera angle for night-vision comparisons and listen through the full line for audio checks.
On an exact reported anomaly match, public guides direct players to turn off the porch light. When the view or sound is incomplete, hold the decision and recheck.
Return to the visitor table and use the alias chips. Names vary between Police Man/Police Officer, Classmate/Homework Kid, and Secret Agent/FBI Agent.
Use the maps-and-systems route before making a door decision. A wrong view cannot validate a clue.
A screenshot can miss audio, motion, or a normal-versus-night-vision change.
The public guides describe a consequence-bearing choice. Unclear evidence should be rechecked, not converted into a universal deny rule.
No. Learn the evidence loop and keep the visitor index nearby.
