Naming every odd detail an anomaly
Replacement: compare what changed and how the interface responds.
Anomaly behavior can change during alpha. Use a response pattern that works before you have memorized every character or scare.
When something changes unexpectedly, stop starting new service actions. Say what changed and where you saw it. Keep the team together long enough to compare the room, then use the current objective and visible interface to decide whether to inspect, wait or return to service. Do not turn one uncertain sighting into a confident rule for the next run.
Action route
Finish or safely leave the action in front of you; do not send every player in a different direction.
Describe the object, character, sound or room area that changed without adding a theory.
Confirm who saw it, who is safe and whether the visible HUD changed.
Once the room is stable, re-read the objective and choose one next action.
Decision table
Recovery
Replacement: compare what changed and how the interface responds.
Replacement: use the visible objective and team observation for the run in front of you.
Replacement: keep one player aware of the order state when it is safe to do so.
Quick answers
This page avoids publishing names and counters that are not stable enough yet. Use the response checklist for the version you are playing.
Not automatically. First compare what changed, then keep only the people needed on the inspection while the rest hold the shift state.